Closed
Bug 691118
Opened 14 years ago
Closed 14 years ago
"ASSERTION: aPrevFrame must be the last continuation in its chain!"
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
mozilla12
People
(Reporter: jruderman, Assigned: ehsan.akhgari)
References
Details
(Keywords: assertion, testcase)
Attachments
(3 files, 1 obsolete file)
###!!! ASSERTION: aPrevFrame must be the last continuation in its chain!: '!aPrevFrame || (!aPrevFrame->GetNextContinuation() || IS_TRUE_OVERFLOW_CONTAINER(aPrevFrame->GetNextContinuation())) && !IS_TRUE_OVERFLOW_CONTAINER(aPrevFrame)', file layout/base/nsFrameManager.cpp, line 497
| Reporter | ||
Comment 1•14 years ago
|
||
Comment 2•14 years ago
|
||
Caused by something between fc7e928eaeae and af3668a89015, ie bug 10209.
Blocks: 10209
| Assignee | ||
Comment 3•14 years ago
|
||
I don't think that the assertion actually makes any sense for absolute frames.
Why's that?
| Assignee | ||
Comment 5•14 years ago
|
||
Because we're not appending a frame after aPrevFrame. Or at least, it should be possible to append an absolute frame in that case.
aPrevFrame would be the previous abs-pos frame.
| Assignee | ||
Comment 7•14 years ago
|
||
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #6)
> aPrevFrame would be the previous abs-pos frame.
But still, does the assertion make sense? We don't require abs-pos frames to be overflow containers, right?
They can't be true overflow containers, actually. See the definition of IS_TRUE_OVERFLOW_CONTAINER.
I think probably instead of checking IS_TRUE_OVERFLOW_CONTAINER we should just check for the NS_FRAME_IS_OVERFLOW_CONTAINER state bit.
| Assignee | ||
Comment 9•14 years ago
|
||
Attachment #565635 -
Attachment is obsolete: true
Attachment #565635 -
Flags: review?(roc)
Attachment #585539 -
Flags: review?(roc)
Attachment #585539 -
Flags: review?(roc) → review+
| Assignee | ||
Comment 10•14 years ago
|
||
Flags: in-testsuite+
Target Milestone: --- → mozilla12
Comment 11•14 years ago
|
||
Try run for 689ef914ab82 is complete.
Detailed breakdown of the results available here:
https://tbpl.mozilla.org/?tree=Try&rev=689ef914ab82
Results (out of 208 total builds):
exception: 3
success: 181
warnings: 23
failure: 1
Builds (or logs if builds failed) available at:
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/eakhgari@mozilla.com-689ef914ab82
Comment 12•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•