Closed Bug 422502 Opened 17 years ago Closed 9 years ago

xsl:include fails in chrome in beta4, works when loaded normally

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tobyschachman, Unassigned)

References

()

Details

(Keywords: regression)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4 When I use javascript's XSLTProcessor with an XSL file from a chrome url, xsl:include doesn't work. This happens as of Firefox beta 4. No reason is given, but importStylesheet fails. The XSL file works when it (and the included file) are not in chrome. I assume there's some security thing that was added in beta 4. Reproducible: Always Steps to Reproduce: 1. Take the attached folder and put it somewhere where it can be accessed via a chrome url. 2. Load test.html (via a chrome url) in FF beta 4. Actual Results: importStylesheet (line 17) fails: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXSLTProcessor.importStylesheet]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://.../test.html :: <TOP_LEVEL> :: line 17" data: no] Expected Results: Should alert "trivialtransformation". This works if you have the files not in chrome.
Component: General → DOM
Keywords: regression
OS: Mac OS X → All
Product: Firefox → Core
QA Contact: general → general
Version: unspecified → Trunk
Note that 499241 was reported against FF 3.5 beta 4, but this bug was reported against 3.0 beta 4
The error is still the same: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXSLTProcessor.importStylesheet]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://../../xslincludetest/test.html :: <TOP_LEVEL> :: line 17" data: no] Indeed when I try a 5 March 2008 build I get the same error. Maybe it was fixed and has regressed again. Or for some other reason the testcase started to fail again.
This is still a problem in the 3.5 release. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5
This is still a problem in aurora 10.0a2 release. Mozilla/5.0 (X11; Linux i686; rv:12.0a2) Gecko/20120212 Firefox/12.0a2
This bug has been tagged for regression and or closure. I cannot produce the error messages in Nightly or Release Considering this I will mark this issue as Resolved-WORKSFORME. If anyone can still reproduce it, feel free to reopen the issue and provide updated steps/links.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: