Closed
Bug 535911
Opened 15 years ago
Closed 15 years ago
"ASSERTION: aParentFrame has later continuations with kids?" with -moz-column
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: bzbarsky)
References
Details
(Keywords: assertion, testcase)
Attachments
(2 files)
543 bytes,
application/xhtml+xml
|
Details | |
6.16 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
###!!! ASSERTION: aParentFrame has later continuations with kids?: 'nextSibling || !aParentFrame->GetNextContinuation() || !aParentFrame->GetNextContinuation()->GetFirstChild(nsnull)', file /Users/jruderman/mozilla-central/layout/base/nsCSSFrameConstructor.cpp, line 5792
Assignee | ||
Comment 1•15 years ago
|
||
This is effectively a regression from bug 531148 but in this case the assert is actually bogus. I should probably refactor some of this stuff into a DoAppendFrames that doesn't assert this assertion (because it's false in the recursive call case, as seen here).
Blocks: 531148
Assignee | ||
Comment 2•15 years ago
|
||
This is ugly, but having a DoAppendFrames would involve either putting the "get the next sibling" code into a debug-only block in AppendFrames or something. That code is needed on both the recursive codepath or the other one. Alternately, I could make the argument non-debug-only, or I could make the asserts assert only if the first new frame is not the special sibling of aPrevSibling. Let me know.
Comment on attachment 418961 [details] [diff] [review] Possible fix I would just make the function always take the aIsRecursiveCall parameter, debug or not.
Attachment #418961 -
Flags: review?(roc) → review+
Assignee | ||
Comment 4•15 years ago
|
||
Pushed http://hg.mozilla.org/mozilla-central/rev/8e1185b4a132 with that change.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•