Bug 86358 – Use of #160 in input causes XSLT to fail in text/html page

• Component: XML
• Status: NEW

[David Carlisle]

Created attachment 141691 [details]
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

[Ahmad Saleem]

This is still reproducible in Safari 15.5 and Chrome Canary 104, both report back "Bad" while Firefox shows "Good" upon clicking "run xslt" button. Thanks!