Closed
Bug 322688
Opened 19 years ago
Closed 19 years ago
ASSERTION: next-in-flow has different content: '!kidFrame || parentFrame->GetContent() == aParentContent'
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
People
(Reporter: martijn.martijn, Assigned: MatsPalmgren_bugz)
References
Details
(Keywords: assertion, testcase)
Attachments
(3 files)
471 bytes,
text/html
|
Details | |
19.74 KB,
text/html
|
Details | |
3.96 KB,
patch
|
roc
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
See upcoming testcase, it gives this assertion on load in a recent debug Firefox build:
###!!! ASSERTION: next-in-flow has different content: '!kidFrame || parentFrame-
>GetContent() == aParentContent', file c:/mozilla/mozilla/layout/base/nsCSSFrame
Constructor.cpp, line 11092
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Updated•19 years ago
|
Summary: SSERTION: next-in-flow has different content: '!kidFrame || parentFrame->GetContent() == aParentContent' → ASSERTION: next-in-flow has different content: '!kidFrame || parentFrame->GetContent() == aParentContent'
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → mats.palmgren
OS: Windows XP → All
Hardware: PC → All
Assignee | ||
Comment 2•19 years ago
|
||
http://webtools.mozilla.org/bonsai/cvsblame.cgi?file=mozilla/layout/base/nsCSSFrameConstructor.cpp&rev=1.1172&root=/cvsroot&mark=11092-11096,11100,11104-11107,11110#11061 We're looking for content (cyan) in a descendent of aParentFrame (red). Starting at the "hint frame" (blue) [line 11092] (since it's an out-of-flow we change it to the placeholder [11095]), the placeholder has no next sibling [11100] so we try to find a next-in-flow/special-sibling for the parent [11106] so we can continue with that frame's first child [11110]. This seems reasonble, the problem is that we are using the original hint frame, an out-of-flow in this case, whos parent (yellow) in this case happens to have a special sibling (lime)... It's content is different from |aParentFrame| (pink) hence the assert. I think the correct algorithm would be to look at the parent of the placeholder and see if that has any next-in-flow/special-sibling and continue with its first child if any. That is the next in-flow child that follows after the hint.
Assignee | ||
Comment 3•19 years ago
|
||
roc, I saw your name in this method, maybe you can review? The patch uses the parent of the placeholder, not the out-of-flow.
Attachment #207917 -
Flags: superreview?(bzbarsky)
Attachment #207917 -
Flags: review?(roc)
Comment 4•19 years ago
|
||
Comment on attachment 207917 [details] [diff] [review] Patch rev. 1 I think this makes sense... we really need to think about making this whole setup simpler. :(
Attachment #207917 -
Flags: superreview?(bzbarsky) → superreview+
Attachment #207917 -
Flags: review?(roc) → review+
Assignee | ||
Comment 5•19 years ago
|
||
Checked in on trunk at 2006-01-15 15:44 PDT. -> FIXED
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•