[Webkit-unassigned] [Bug 86358] New: Use of #160 in input causes XSLT to fail in text/html page
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon May 14 04:39:57 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=86358
Summary: Use of #160 in input causes XSLT to fail in text/html
page
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: XML
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: davidc at nag.co.uk
Created an attachment (id=141691)
--> (https://bugs.webkit.org/attachment.cgi?id=141691&action=review)
test file for running xslt on an element containing #160
Using XSLTProcessor to process an html element that contains the numeric reference "& # 1 6 0 ;" causes the XSLT processor to return null rather than a node.
I suspect (but don't really have the tools to confirm) that the XSLT engine is being passed a serialisation using " & n b s p ;" which is then failing to parse as XML as the entity is not defined in that context.
To reproduce, load attached html page and click on "run xslt" button. If XSLT runs, then the text of the following paragraph changes to "Good". If it does not run then it changes to "Bad".
Results with different browsers
Bad: Safari 5.1.7
Bad: Webkit Nightly WebKit-r116595
Bad: Chrome 20.0.1132.3 dev-m
Good: Opera 11.62
Good: Firefox Nightly 15.0a1 (2012-05-11)
IE: doesn't support XSLTProcessor
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list