Bug 60664 – Implement unparsed-entity-uri() XSLT function in Webkit

• Component: XML
• Status: RESOLVED INVALID

[Alejandro Araneda]

Created attachment 93188 [details]
XML with XSLT stylesheet

Both IE and Opera correctly render the attached XML document.

Because Webkit browsers cannot even handle an unparsed external entity declaration in the DTD's internal subset breaks the XML parser, it might be this issue what is blocking the implementation of XSLT's function unparsed-entity-uri.

Do note that there is a bug entry for Firefox also at https://bugzilla.mozilla.org/show_bug.cgi?id=65981

[Alexey Proskuryakov]

libxslt supports unparsed-entity-uri, so I think that the inability to parse this source is likely the only issue here.

[Alejandro Araneda]

(In reply to comment #1)
> libxslt supports unparsed-entity-uri, so I think that the inability to parse this source is likely the only issue here.

Should I commit a new entry about this or there is one already?

[Alejandro Araneda]

This was a confusion over the specification RFC 3986. According to http://tools.ietf.org/html/rfc3986#section-4.4

'The most frequent examples of same-document references are relative references that are empty or include only the number sign ("#") separator followed by a fragment identifier.'

Now that the example has been corrected, both Chrome and Safari properly output the result of "unparsed-entity-uri()" function.