Closed
Bug 195375
Opened 22 years ago
Closed 20 years ago
When print()ing from a frame with height 0, an unprintable job occupies the queue
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 197556
People
(Reporter: vroemisse, Assigned: rods)
Details
Attachments
(1 file)
435 bytes,
application/octet-stream
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.3b) Gecko/20030210
What I've been trying to do is load a printer-friendly page in an invisible
frame (height 0) after the user clicks a print link. In the page there is a
javascript print() command, either in the body onload or somewhere near the
bottom of the page - it doesn't make a difference for the behaviour.
What happens is a print dialog pops up and after clicking ok, the printing
dialog appears saying it is preparing the printing. It won't go away by itself
though. Clicking the x makes it go away, leaving a job in the printer queue that
just keeps sitting there. When I set the frame height to 1 or more, all works as
expected.
Reproducible: Always
Steps to Reproduce:
1. Create a frame with height 0
2. Load a page in the frame that has a print() command somewhere in the page
3. Load frameset
4. Click ok in the print dialog
5. Wait
6. Wait
7. Click x in the printing pop-up window
Actual Results:
See details.
Expected Results:
I'd have expected the page to be printed like it does if the frame height is > 0.
Reporter | ||
Comment 1•22 years ago
|
||
Reporter | ||
Comment 2•22 years ago
|
||
Oh, the printing progress pop-up doesn't always appear. The job that won't print
always does though.
Comment 3•22 years ago
|
||
reporter: Does it work in newer builds?
Reporter | ||
Comment 4•22 years ago
|
||
Nope, the problem is still there in win32-1.4rc1
Comment 5•20 years ago
|
||
*** This bug has been marked as a duplicate of 197556 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•