Closed Bug 1223332 Opened 10 years ago Closed 10 years ago

nsDeviceContext::EndDocument is sometimes called when nsDeviceContext::BeginDocument hasn't been called.

Categories

(Core :: Printing: Output, defect)

Product:
Core
Component:
Printing: Output
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bobowen, Unassigned)

References

Details

While test for bug 1156742, I've noticed that nsDeviceContext::EndDocument is sometimes called in an error situation even when nsDeviceContext::BeginDocument hasn't been called yet. This doesn't make much sense to me and is probably down to some incorrect logic somewhere.
I'm pretty sure this was just in my patches, because I wasn't waiting for the InitializePrint call to the parent to complete, before continuing.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You left a reference to this bug in the code.
Flags: needinfo?(bobowencode)
Yeah, I wasn't totally sure that it couldn't happen for some other reason.
Flags: needinfo?(bobowencode)
You need to log in before you can comment on or make changes to this bug.