Bug 4359
| Summary: | Failure of XPath/document() within XSLT | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Sinz <Michael.Sinz> |
| Component: | XML | Assignee: | Dave Hyatt <hyatt> |
| Status: | RESOLVED FIXED | ||
| Severity: | Major | ||
| Priority: | P2 | ||
| Version: | 312.x | ||
| Hardware: | Mac | ||
| OS: | OS X 10.3 | ||
| URL: | http://svn.sinz.com/browser-tests/test3.html | ||
Michael Sinz
Loading a relative path document (the recommended mechanism) within an XSLT
transform fails in Safari in 10.3.9 and 10.4 systems.
This can be easily seen in the http://svn.sinz.com/browser-tests/test3/index.xml
page, which uses the document() mechanism to load some shared
template/configuration data from the server rather than having it within each of
the XSLT documents.
This failure may be related to the same problem in bug #4054 where the
XMLHttpRequest object is blocked from sending a request back to the originating
server if the page was an XML/XSLT based page. The exact same code works fine
if the page was XSLT transformed on the server and thus only HTML got served to
the client (and JavaScript)
If this is related to bug #4054 (which I believe it is), I would classify this
as a major bug as it causes all manner of downstream problems and may have
actual web security model implications which may even be useable in an exploit
(I have not had time to try to build such an exploit if it is even possible -
the concept is that with XML/XSLT and JavaScript within the generated HTML page,
it may be that the security context would show up as local, thus allowing access
to items that would otherwise should not be possible)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Reporter, please verify this and related bugs against ToT. Some of them seem to be fixed - maybe by a fix
in bug 5219, but I'm far from being sure.
If it's possible to make simplified standalone versions of the test pages, I think it would still be useful to
have them as regression tests.
Michael Sinz
If you think the fix for bug 5219 has fixed this, maybe it fixed bug 4054?