XSLT document function fails silently
Reported by
m...@shmarya.net,
May 4 2017
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. unzip ajax_xsl.zip 2. run server in ajax_xsl directory (e.g. `python -m SimpleHTTPServer 8000`) 3. browse to http://localhost:8000/page.xhtml What is the expected behavior? The file.xsl file should retrieve the test.xml additional xml file from the server via the document XSLT function, resulting in "success" being printed on the page What went wrong? The XSLT document function fails silently, returning null. No request is made to the server Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.133 Channel: stable OS Version: 4.2.0-42-generic Flash Version: This is NOT a same origin policy error, as the original origin is being used. I tried to debug this some, and found that everything is alright until this line: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/xml/XSLTProcessorLibxslt.cpp?l=128 For some reason, the resource->ResourceBuffer() returns null.
,
May 4 2017
I also tried this against a TOT chromium compiled for android. Same behavior.
,
May 4 2017
I just noticed that if I navigate directly to the file.xml file, which has an xml-stylesheet tag pointed at file.xsl, everything works as expected.
,
May 10 2017
,
May 11 2017
,
Jul 21 2017
Confirmed. Safari doesn't work too.
,
Jul 23
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 25
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by m...@shmarya.net
, May 4 2017