[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Fwd: Fwd: Re: Bug#1472: kfm won't render this page
From:       David Faure <david.faure () insa-lyon ! fr>
Date:       1999-06-27 13:18:51
[Download RAW message or body]

----- Forwarded message from Dawit Alemayehu <adawit@earthlink.net> -----

From: Dawit Alemayehu <adawit@earthlink.net>
To: faure@kde.org
Subject: Fwd: Re: Bug#1472: kfm won't render this page
Date: 	Sun, 27 Jun 1999 06:00:02 -0400


Here is the second part of the message ...

Dawit A.

----------  Forwarded Message  ----------
Subject: Re: Bug#1472: kfm won't render this page
Date: Fri, 25 Jun 1999 19:49:30 -0400
From: Dawit Alemayehu <adawit@earthlink.net>


On Fri, 25 Jun 1999, David Faure wrote:
On Fri, Jun 25, 1999 at 10:34:24AM -0300, Hume Smith wrote:
> package: kfm 
> version: kfm-1.167.2.11 
> 
> <URL:http://www.glinx.com/~hclsmith/> 

Ahhhhh... And I also know the problem with the second URL.  KFM renders this
page correctly except the images for some links.  This is due to a previously \
reported bug that was discussed in this list before. The author of the page uses that
weird but valid URL format. As an example, here is one of the links on the page

<a href="//www.operasoftware.com/"><img \
src="//www.operasoftware.com/graphics/opera_bu.gif" alt="Opera" width=88 \
height=31></a>

khtmlw ( and khtml <- I am not sure since I have not checked it  ) interpret
the address in HREF as a relative URL.  Hence,  the base or the document URL is
incorrectly applied to obtain the absolute path.  Actually, this problem
looks like the failing of KURL as it does not correctly recognize such URL(s).
Anyway, if you put your mouse over this link ( first one on the page ), the
status bar displays the location as

http://www.glinx.com/www.operasoftware.com

This can easily be patched as I have done with minicli (kdebase/kwm/minicli.C )
and am going to do for kfm's location box.   However, I have to find out where khtml
and khtmlw deal with links in order to try and fix it.  Moreover, IMHO the long term
solution should be to fix KURL instead of all the application that make use of it ...

Regards,
Dawit A.
-------------------------------------------------------

----- End forwarded message -----

-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today


[prev in list] [next in list] [prev in thread] [next in thread]