Closed
Bug 248318
Opened 21 years ago
Closed 21 years ago
javascript error with http/https URIs in frames
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 246923
People
(Reporter: nis.martensen, Assigned: bugzilla)
References
()
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040622 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040622 Firefox/0.8.0+ Firfox 0.9 gives Error: uncaught exception: [Exception... "Access to property denied" code: "1010" nsresult: "0x805303f2 (NS_ERROR_DOM_PROP_ACCESS_DENIED)" location: "https://www.eev.e-technik.tu-darmstadt.de/moztest/unten.html Line: 16"] when clicking on the links in the bottom frame; firefox 0.8 works. Reproducible: Always Steps to Reproduce: 1. Open JavaScript Console 2. Go to http://www.eev.e-technik.tu-darmstadt.de/~nmartensen/ 3. Click on the links in the bottom frame Actual Results: content of top frame does not change, javascript error instead Expected Results: change content of top frame This is a problem in our internal pages. I created the above frameset as minimal example. The error only occurs when content pages of both frames are on https URI while the URI of the frameset definition is not. When I move the content of the bottom frame to non-https location, things work again (https pages will be shown in top frame). Setting docshell.frameloadcheck.disabled to true as mentioned in the release notes works around this problem.
Comment 1•21 years ago
|
||
This page doesn't use nested frames, so I wonder why the patch from bug 246448 broke it. Does the patch in bug 246923 fix it?
Comment 2•21 years ago
|
||
Yup, it does. *** This bug has been marked as a duplicate of 246923 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•