354481 - Cannot access css styles by javascript on HTTPS

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[coviex]

User-Agent:       Opera/9.02 (Windows NT 5.1; U; en)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

The document.styleSheets[0].cssRules collection which available in HTTP is not available in HTTPS.

Reproducible: Always

Steps to Reproduce:
1. access some page containing alert(document.styleSheets[0].cssRules) by HTTP
2. this will result in proper object dump to GUI
3. access the same page but by HTTPS
4. this will result in javascript error
Actual Results:  
got error

Expected Results:  
regular alert result

Here is error message:

[Exception... "Access to restricted URI denied" code: "1012" nsresult: "0x805303f4 (NS_ERROR_DOM_BAD_URI)" location: "http://www.server.com/project/js/script.js Line: 849"]

And it doesn`t matter whether css or js file is included by HTTP or HTTPS.

Comment 1

[Jesse Ruderman]

Attachment: Jesse's testcase

Comment 2

[Jesse Ruderman]

WFM with my testcase.  I see "[object CSSRuleList]" when I load it.

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060928 Minefield/3.0a1

Comment 3

[Steve England [:stevee]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a6pre) Gecko/20070615 Minefield/3.0a6pre ID:2007061504
Me too. --> WORKSFORME?

Comment 4

[u88484]

This bug was reported using a version of Firefox that security and stability updates are no longer provided for.  All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html

If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'.

If you can still reproduce this bug, please provide additional details to help resolve this issue.

Comment 5

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please reply if you can still reproduce this bug with Firefox 3.5.3 or later in a new profile with the latest plugins (flash, quicktime, java, etc.).