Closed
Bug 286869
Opened 20 years ago
Closed 20 years ago
[FIX]bogus assertion ASSERTION: Unexpected ContentAppended: '!mIsDocumentGone during print preview
Categories
(Core :: Layout, defect, P1)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla1.8beta2
People
(Reporter: bernd_mozilla, Assigned: bzbarsky)
References
()
Details
Attachments
(1 file)
|
3.70 KB,
patch
|
roc
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
due to the checkin for bug 281957
print preview is currently a pain
steps to reproduce load any page into print preview
move cursor
|
Assignee | |
Comment 1•20 years ago
|
||
So what's going on here is that printing is just completely bogus... It sets up
a presshell, does a reflow, disconnects the presshell from the document, then,
in nsPrintEngine::FinishPrintPreview hooks the same exact presshell to the document.
I'll add hacks to PresShell to deal with this, but could you please file a
separate bug on printing code to not do this crap? :(
|
|
Assignee | |
Comment 2•20 years ago
|
||
Most of this is just fixing assert tests; the only interesting part is in
BeginObservingDocument.
Attachment #178341 -
Flags: superreview?(roc)
Attachment #178341 -
Flags: review?(roc)
|
|
Assignee | |
Updated•20 years ago
|
Summary: bogus assertion ASSERTION: Unexpected ContentAppended: '!mIsDocumentGone during print preview → [FIX]bogus assertion ASSERTION: Unexpected ContentAppended: '!mIsDocumentGone during print preview
|
|
Assignee | |
Updated•20 years ago
|
OS: Windows XP → All
Priority: -- → P1
Hardware: PC → All
Target Milestone: --- → mozilla1.8beta2
Attachment #178341 -
Flags: superreview?(roc)
Attachment #178341 -
Flags: superreview+
Attachment #178341 -
Flags: review?(roc)
Attachment #178341 -
Flags: review+
|
|
Assignee | |
Comment 3•20 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Product: Core → Core Graveyard
|
||
Updated•7 years ago
|
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•