Supporting legacy <image>

Germain Garand germain at ebooksfrance.org
Fri Oct 10 16:52:56 BST 2008


Le dimanche 5 octobre 2008, Harri Porten a écrit :
> Hi!
>
> Some reworking of our tag name representation (r867535) broke support for
> legacy HTML elements. The question is do which degree we want to fix or
> drop that. The misc/maketags made the following elements equivalent
>
>     image -> img
>     anchor -> a
>     listing -> pre
>
> for pre HTML 4 compat. I've put up a test on
> http://www.froglogic.com/~porten/compat.html that tests both HTML parsing
> and createElement() DOM calls for those three. Results:
>
>    - neither Firefox, IE nor Opera special case "anchor" and "listing". I
> was not able to find any sign of <anchor> btw.
>

'listing' is not aliased to 'pre' in firefox or opera, but it still gets 
treated exactly as a 'pre' in those browsers... so I intend to commit the 
attached to fix the two changes this caused in baseline[1].

Germain

[1] webcore/fast/html/listing.html
    basics/listing.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-reinstate-handling-of-legacy-listing-tag.patch
Type: text/x-diff
Size: 16452 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20081010/56387df8/attachment.patch>


More information about the kfm-devel mailing list