Closed
Bug 538070
Opened 15 years ago
Closed 15 years ago
"ASSERTION: Our frame tree is likely to be bogus!" with xbl, xul:listcell
Categories
(Core :: XBL, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
|
(deleted),
application/xhtml+xml
|
Details |
###!!! ASSERTION: Must have parent here: 'aContent->GetParent()', file layout/base/nsCSSFrameConstructor.cpp, line 4550
###!!! ASSERTION: Reparenting something that has no usable parent? Shouldn't happen!: 'Not Reached', file layout/base/nsFrameManager.cpp, line 792
###!!! ASSERTION: Our frame tree is likely to be bogus!: '!(styleChange & nsChangeHint_ReconstructFrame)', file layout/base/nsFrameManager.cpp, line 864
|
||
Comment 1•15 years ago
|
||
The good news is that I don't see any of these asserts in my build. I bet money, based on examination of the testcas, that the second patch for bug 514300 fixes this. I can verify by locally qpopping if desired...
Depends on: 514300
|
|
||
Comment 2•15 years ago
|
||
The fix for bug 514300 should have fixed this. Jesse, can you retest?
If it's fixed, do we want to just push the testcase, or wait until we get bug 514300 on branches?
|
Reporter | |
Comment 3•15 years ago
|
||
I can't reproduce even at rev 50a66336ba73, before that fix landed. So something else must have fixed this testcase.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
|
||
Updated•9 years ago
|
Group: core-security → core-security-release
|
||
Updated•9 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•