Closed
Bug 340092
Opened 20 years ago
Closed 17 years ago
Security error accessing cssRules via DOM after setting document.domain
Categories
(Core :: DOM: CSS Object Model, defect)
Core
DOM: CSS Object Model
Tracking
()
RESOLVED
INVALID
People
(Reporter: steve, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file, 1 obsolete file)
|
650 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
This is new in 1.5.04
The following, which has worked in every version of FF to date...
var styleSheet = GL_GetStyleSheet("column_widths");
var rules = styleSheet.cssRules;
now causes this...
[Exception... "Access to restricted URI denied" code: "1012" nsresult: "0x805303f4 (NS_ERROR_DOM_BAD_URI)" location: "http://steve.caplin.com/SL4B/webcentric_caplin/script/view/html_grid.js Line: 119"]
Reproducible: Always
Steps to Reproduce:
1. get a reference to a stylesheet object
2. try to access the cssRules collection
3. (may be signigficant, document.domain has been set)
this is a critical bug for my application FW, which depends on this behaviour.
| Reporter | ||
Comment 1•20 years ago
|
||
correction to this report: I just rolled back to 1.5.03 and still see the bug. I think the cause is that I wasn't previously setting document.domain and then it worked. For further info, I'm accessing an inline stylesheet (style block) declared in the html page from which the script has been loaded. The domain is set to the same domain from which the page was loaded. For all I know, this bug has always been here. Reminds me of the bug whereby I cannot access responseXML.documentElement on XMLHTTPRequest object after document.domain has been set (even though I can still accesss responseText ! I'm sure this one has been reported separately).
My app no longer supports firefox until this one gets foxed (IE and Safari only)
Comment 2•19 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
Comment 3•18 years ago
|
||
I have just encountered this problem:
Firefox 2.0.0.6
I have an html page that includes stylesheets as
<link title="t1" id="t1" rel=stylesheet type="text/css" href="/css/t1.css">
I can access the DOM document.styleSheets[myidx].cssRules (etc) fine.
UNTIL, I put document.domain = "mydomain.com" (with the correct domain of course) on my pages. As soon as I do that, the moment I try to reference the "cssRules" property of the sheet object, I get the access denied error given above.
This is a very bad problem for me.
I am having the same problem too, after I put document.domain = "mydomain.com"; in the javascript, all the CCS and everything **** out. No problems with IE, is someone going to fix this?
Comment 6•18 years ago
|
||
Still present in Firefox 2.0.0.10.
Harry: you could always put up a job at rentacoder.com or similar, producing a patch that fixes the problem (likely that the styleSheets[n] object does not also get its domain changed with the document, or that the security test fails to take document.domain into consideration). With a bit of luck, posting the fix here gets it into upstream Firefox builds.
Comment 7•18 years ago
|
||
OS is probably "ALL"; I confirmed it on the MacOS X build.
Comment 8•17 years ago
|
||
Can someone confirm this bug still occurs in Firefox 3 please?
Whiteboard: CLOSEME 06/27
Comment 9•17 years ago
|
||
Comment 10•17 years ago
|
||
Attachment #341698 -
Attachment is obsolete: true
Comment 11•17 years ago
|
||
-> CSSOM for further triage
Component: General → DOM: CSS Object Model
Keywords: testcase
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → general
Hardware: PC → All
Version: 1.5.0.x Branch → unspecified
Updated•17 years ago
|
Summary: error accessing cssRules via DOM → Security error accessing cssRules via DOM after setting document.domain
Comment 12•17 years ago
|
||
This is more or less done on purpose, since not doing this would allow stealing data from stylesheets that didn't opt in by setting document.domain.
I'm pretty sure HTML5 will require this behavior.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•