Closed
Bug 233733
Opened 21 years ago
Closed 21 years ago
unable to change iframe's location with frames.location.href
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: mozilla, Assigned: bugzilla)
References
Details
Attachments
(2 files, 2 obsolete files)
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
I've just upgraded from a nightly build in december to the new release of
Firefox 0.8 and have noticed that one of my web pages stopped working. It seems
that the problem is in the method of using frames.location.href to change the
location. I've written up a testcase which demonstrates this.
Reproducible: Always
Steps to Reproduce:
Put both test case files in the same directory and open testcase.html.
a) Click on the first "broken" link.
b) Click the first "works" link
c) Click on the "Security error in the right iframe
Actual Results:
a) Does not change the location of the iframe as expected. Gives "Error:
uncaught exception: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIDOMLocation.href]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame :: <unknown filename> :: onclick ::
line 0" data: no]" in javascript console.
b) Correctly changes the location of the iframe.
c) Does not change the location of the iframe as expected. Gives "Security
Error: Content at http://localhost/testcase-a.html may not load or link to
chrome://browser/content/testcase.html." in javascript console
Expected Results:
All three actions should correctly change the location of the iframe.
This regression (security fix??) breaks a few web pages that work in IE and in
previous versions of Mozilla Fire(bird|fox).
| Reporter | ||
Comment 1•21 years ago
|
||
| Reporter | ||
Comment 2•21 years ago
|
||
Comment 3•21 years ago
|
||
Attachment #141081 -
Attachment is obsolete: true
Comment 4•21 years ago
|
||
Attachment #141100 -
Attachment is obsolete: true
Updated•21 years ago
|
Attachment #141100 -
Attachment description: Usable version of testcase; LOAD THIS → Usable version of testcase
Comment 5•21 years ago
|
||
The testcase works fine for me (the "broken" links frob bugzilla, the "security
error" links locally once I fixed up the "/testcase.html" stuff to point to the
right file; I can't easily attach two self-referencing things to bugzilla and be
sure it will work, so leaving as-is).
Are you seeing this in a SeaMonkey build? Are you using the TBE extension, by
any chance?
Updated•21 years ago
|
| Reporter | ||
Comment 6•21 years ago
|
||
sorry, i meant to add "for relative urls". Yes, I am using TBE. This problem
happens without it however.
Comment 7•21 years ago
|
||
Well, I can't reproduce this in SeaMonkey, so....
Then again, aebrahim can't reproduce it in firefox either....
Assignee: general → firefox
Component: DOM → General
Product: Browser → Firefox
Version: Trunk → unspecified
| Reporter | ||
Comment 8•21 years ago
|
||
this *is* a TBE bug. I installed Fx on another computer and it worked fine. Then
I disabled TBE on my own computer and restarted Fx and it worked fine as well.
Sorry for wasting your time.
a static version of the test case can be located at
http://burntpopcorn.net/testcase/testcase.html
Comment 9•21 years ago
|
||
Invalid, an extension bug per last comment.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Comment 10•21 years ago
|
||
*** Bug 233683 has been marked as a duplicate of this bug. ***
Comment 11•21 years ago
|
||
*** Bug 233709 has been marked as a duplicate of this bug. ***
Comment 12•21 years ago
|
||
*** Bug 233857 has been marked as a duplicate of this bug. ***
Comment 13•21 years ago
|
||
*** Bug 234158 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•