RESOLVED INVALID 60664
Implement unparsed-entity-uri() XSLT function in Webkit 
https://bugs.webkit.org/show_bug.cgi?id=60664
Summary Implement unparsed-entity-uri() XSLT function in Webkit
Alejandro Araneda
Reported 2011-05-11 14:51:42 PDT
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
Attachments
XML with XSLT stylesheet (34 bytes, text/plain)
2011-05-11 14:51 PDT, Alejandro Araneda 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2011-05-11 22:00:46 PDT
libxslt supports unparsed-entity-uri, so I think that the inability to parse this source is likely the only issue here.
Alejandro Araneda
Comment 2 2011-05-12 05:42:21 PDT
(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
Comment 3 2011-05-13 13:05:05 PDT
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.
Note You need to log in before you can comment on or make changes to this bug.