Closed
Bug 377824
Opened 18 years ago
Closed 18 years ago
[FIX]mtable causes "ASSERTION: Should have dealt with kids that have NS_FRAME_IS_SPECIAL elsewhere"
Categories
(Core :: MathML, defect, P1)
Core
MathML
Tracking
()
RESOLVED
FIXED
mozilla1.9alpha4
People
(Reporter: jruderman, Assigned: bzbarsky)
References
Details
(5 keywords)
Attachments
(2 files)
131 bytes,
application/xhtml+xml
|
Details | |
3.17 KB,
patch
|
dbaron
:
review+
dbaron
:
superreview+
dveditz
:
approval1.8.1.4+
dveditz
:
approval1.8.0.12+
|
Details | Diff | Splinter Review |
Loading the testcase triggers:
###!!! ASSERTION: Should have dealt with kids that have NS_FRAME_IS_SPECIAL elsewhere: 'aChildPseudo != nsCSSAnonBoxes::mozAnonymousBlock && aChildPseudo != nsCSSAnonBoxes::mozAnonymousPositionedBlock', nsFrame.cpp, line 5494
This assertion was added in bug 323656.
Assignee | ||
Comment 1•18 years ago
|
||
Mm.... so MathML is reusing the mozAnonymousBlock pseudo that really only {ib} splits should be using. I suppose we can comment out the assertion until after MathML switches to inline-table, or give MathML its own pseudo.
I'd prefer the latter approach, frankly, but on branches maybe we need to do the former.
Flags: blocking1.8.1.4?
Flags: blocking1.8.0.12?
Assignee | ||
Comment 2•18 years ago
|
||
David, let me know whether you have a preference, ok?
Seems like its own pseudo is better.
I don't think content can style these pseudos, so I don't think there should be any issues for branch.
Assignee | ||
Comment 4•18 years ago
|
||
Assignee: rbs → bzbarsky
Status: NEW → ASSIGNED
Attachment #261912 -
Flags: superreview?(dbaron)
Attachment #261912 -
Flags: review?(dbaron)
Assignee | ||
Updated•18 years ago
|
OS: Mac OS X → All
Priority: -- → P1
Hardware: PC → All
Summary: mtable causes "ASSERTION: Should have dealt with kids that have NS_FRAME_IS_SPECIAL elsewhere" → [FIX]mtable causes "ASSERTION: Should have dealt with kids that have NS_FRAME_IS_SPECIAL elsewhere"
Target Milestone: --- → mozilla1.9alpha4
Updated•18 years ago
|
Flags: blocking1.8.1.4?
Flags: blocking1.8.1.4+
Flags: blocking1.8.0.12?
Flags: blocking1.8.0.12+
Comment on attachment 261912 [details] [diff] [review]
Let's do that.
r+sr=dbaron
Attachment #261912 -
Flags: superreview?(dbaron)
Attachment #261912 -
Flags: superreview+
Attachment #261912 -
Flags: review?(dbaron)
Attachment #261912 -
Flags: review+
Assignee | ||
Updated•18 years ago
|
Attachment #261912 -
Flags: approval1.8.1.4?
Attachment #261912 -
Flags: approval1.8.0.12?
Assignee | ||
Comment 6•18 years ago
|
||
Fixed on trunk.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•18 years ago
|
Flags: in-testsuite?
Comment 7•18 years ago
|
||
Comment on attachment 261912 [details] [diff] [review]
Let's do that.
approved for 1.8.0.12 and 1.8.1.4, a=dveditz for release-drivers
Attachment #261912 -
Flags: approval1.8.1.4?
Attachment #261912 -
Flags: approval1.8.1.4+
Attachment #261912 -
Flags: approval1.8.0.12?
Attachment #261912 -
Flags: approval1.8.0.12+
You need to log in
before you can comment on or make changes to this bug.
Description
•