Closed Bug 426040 Opened 17 years ago Closed 15 years ago

"ASSERTION: Should have dealt with kids that have NS_FRAME_IS_SPECIAL elsewhere" with -moz-column, float

Categories

(Core :: Layout, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jruderman, Unassigned)

References

Details

(Keywords: assertion, testcase)

Attachments

(1 file)

Attached file testcase (deleted) —
Loading the testcase triggers:

###!!! ASSERTION: Should have dealt with kids that have NS_FRAME_IS_SPECIAL elsewhere: 'aChildPseudo != nsCSSAnonBoxes::mozAnonymousBlock && aChildPseudo != nsCSSAnonBoxes::mozAnonymousPositionedBlock', file /Users/jruderman/trunk/mozilla/layout/generic/nsFrame.cpp, line 5477

bz fixed an instance of this assertion in bug 377824, but the testcases are totally different.
So the problem is that GetIBSpecialSibling on the mozAnonymousBlock frame is null.  That's bad.  Shouldn't happen, at all.
So how come all these frames are still in the tree?  When we remove the firstChild of the columnated div, they should all go away.
Patch in bug 413048 fixes this.  Once it lands, we should check in this crashtest.
Depends on: 413048
Flags: in-testsuite?
Crashtest coming soon.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Crashtest added:

http://hg.mozilla.org/mozilla-central/rev/aad5b1c64ed4
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: