Closed
Bug 370255
Opened 17 years ago
Closed 17 years ago
ASSERTION: frame not dirty: 'aFrame->GetStateBits() & (NS_FRAME_IS_DIRTY | NS_FRAME_HAS_DIRTY_CHILDREN)' on changing page direction
Categories
(Core :: Layout: Text and Fonts, defect)
Core
Layout: Text and Fonts
Tracking
()
RESOLVED
FIXED
People
(Reporter: smontagu, Assigned: smontagu)
References
()
Details
Attachments
(2 files)
1.16 KB,
patch
|
uriber
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
509 bytes,
text/html
|
Details |
I get this assertion sometimes when changing page direction from the context menu. Caller is nsContainerFrame::InsertFrames(): #ifdef IBMBIDI if (nsnull == aListName) #endif // Ask the parent frame to reflow me. AddStateBits(NS_FRAME_IS_DIRTY); GetPresContext()->PresShell()-> FrameNeedsReflow(this, nsIPresShell::eTreeChange); The #ifdef IBMBIDI condition should apply to both lines, like the parallel code in nsContainerFrame::AppendFrames
Attachment #254922 -
Flags: superreview?(roc)
Attachment #254922 -
Flags: review?(uriber)
Assignee | ||
Updated•17 years ago
|
Assignee: nobody → smontagu
Comment 1•17 years ago
|
||
Comment on attachment 254922 [details] [diff] [review] Patch Yeah. This is actually a regression from bug 300030 (reflow branch): http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvsroot&subdir=mozilla/layout/generic&command=DIFF_FRAMESET&file=nsInlineFrame.cpp&rev2=3.265&rev1=3.264
Attachment #254922 -
Flags: review?(uriber) → review+
Attachment #254922 -
Flags: superreview?(roc) → superreview+
Assignee | ||
Comment 2•17 years ago
|
||
Checked in.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•17 years ago
|
Flags: in-testsuite? → in-testsuite-
Comment 3•17 years ago
|
||
This can indeed be tested -- it requires setting the appropriate environment variable to make assertions cause a crash. We need a test harness which runs in this manner and is graphical (xpcshell tests run with assertions fatal already, but you don't get any graphical capabilities) to properly write a testcase to ensure the assertion isn't violated in the future in this manner (bug 368573).
Flags: in-testsuite- → in-testsuite?
Comment 4•17 years ago
|
||
(In reply to comment #3) > This can indeed be tested -- it requires setting the appropriate environment > variable to make assertions cause a crash. Or we could scrape the logs for assertions.
Assignee | ||
Comment 5•17 years ago
|
||
In the meanwhile, here is a testcase that asserts on load in builds without the patch.
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: layout.bidi → layout.fonts-and-text
You need to log in
before you can comment on or make changes to this bug.
Description
•