Closed
Bug 344216
Opened 18 years ago
Closed 14 years ago
"ASSERTION: Adding child where we already have a child? This will likely misbehave" with script-added <xul:iframe> on reload
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
437 bytes,
application/vnd.mozilla.xul+xml
|
Details |
Loading the testcase causes "ASSERTION: Adding child where we already have a child? This will likely misbehave". Bug 314457 and bug 307241 are also about this assertion, but they have different testcases and I can't reproduce the assertion with those testcases.
Reporter | ||
Comment 1•18 years ago
|
||
Reporter | ||
Comment 2•17 years ago
|
||
Still happens on trunk with this testcase.
Reporter | ||
Comment 3•17 years ago
|
||
This assertion also shows up on every keypress on http://htmledit.squarefree.com/, which is pretty annoying.
Comment 4•17 years ago
|
||
That seems odd, and worth a separate bug. All we need then is someone to own this code and debug these assertions.. This bug is more or less bug 314457 as far as I can tell.
Depends on: 314457
Reporter | ||
Comment 5•17 years ago
|
||
Ok, I filed bug 396836 on that.
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
Comment 6•15 years ago
|
||
The testcase gives the identical stack as the one on bug 462076 which already has a WIP patch.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Comment 7•15 years ago
|
||
The same stack does NOT mean it's a duplicate. Please mark dependent if you think the other patch might fix this bug. This eager dup-marking is a great way to miss fixing issues.
Comment 8•14 years ago
|
||
This should be fixed by bug 462076 and the disable-xul-in-web-content.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•