Closed Bug 305104 Opened 19 years ago Closed 19 years ago

NS_ERROR_NOT_INITIALIZED when changing iframe location immediately after creation

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 304882

People

(Reporter: bugzilla, Assigned: jst)

References

Details

(Keywords: regression)

Attachments

(2 files)

When creating and appending a new iframe using JavaScript, the location cannot
be immediately set after creation with 20050817, but can with 20050816. The
error thrown to the JavaScript console is:

Error: [Exception... "Component not initialized"  nsresult: "0xc1f30001
(NS_ERROR_NOT_INITIALIZED)"  location: "JS frame ::
file:///C:/Desktop/testcase.html :: runTestcase :: line 14"  data: no]
Source File: file:///C:/Desktop/testcase.html
Line: 14

I'll attach a testcase and a workaround shortly. This is probably something that
should be fixed, since I can imagine this being used in real-world situations.
CC'ing jst because of probable relation to the split window feature.
Attached file Minimised testcase
Nominating 1.8b4. Although there's an easy workaround, this probably breaks some
websites and probably shouldn't.
Flags: blocking1.8b4?
Assignee: nobody → jst
Flags: blocking1.8b4? → blocking1.8b4+
I bet this will be fixed by bug 304882. Duping.

*** This bug has been marked as a duplicate of 304882 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.8b4+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: