[Webkit-unassigned] [Bug 14530] XSLT processing doesn't preserve certain XML DOM trees when the output is HTML

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=14530


ap at webkit.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ap at webkit.org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
            Summary|<img>fallback</img> should  |XSLT processing doesn't
                   |not display the contents of |preserve certain XML DOM
                   |the image element by default|trees when the output is
                   |in XML processed documents  |HTML




------- Comment #3 from ap at webkit.org  2007-07-05 13:22 PDT -------
> It could be omitted for WebKit.

Right - but then this issue no longer happens. So, this bug is actually about a
difference in XSLT processing.

The difference is that WebKit creates a text of XSLT transformation result, and
parses it, while Firefox/Opera operate on DOM nodes. Since the stylesheet has
output method="html", WebKit correctly parses 
'<img src="fake.png"><b>rich</b> fallback</img>'
as 
'<img src="fake.png"><b>rich</b> fallback', and thus the "rich fallback" text
is visible.

On the other hand, Firefox and Opera create a document that cannot be even
serialized to HTML, because its IMG elements have child nodes.

I'm confirming this as a difference with Firefox and Opera, but my
understanding is that WebKit is actually correct here, as the result of XSLT
transformation is conceptually HTML source text.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.