Closed
Bug 141030
Opened 22 years ago
Closed 10 years ago
[REPRO]Status bar for printing does not go away (yet again...)
Categories
(Core :: Printing: Output, defect, P4)
Tracking
()
RESOLVED
INCOMPLETE
Future
People
(Reporter: amitkuchu, Unassigned)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 I see that the 'progress bar' DOES NOT dissapear when i try to print a selection. Reproducible: Always Steps to Reproduce: 1.Goto hotjobs.com and search for a new job for yourself :) (But dont leave mozilla development!!!). Select one of the jobs for "detailed" descriptions. 2.On the right-hand top, there is a link "Print this job description". Click that. 3.On the new window that pops up, select some text, and try to print the selection. Actual Results: 1. The print "progress bar" window pops up but stays there long after the selection has been printed. 2. I have to use 'Cancel' to close the popup. Expected Results: The status windows should disappear after printing is completed.
Comment 1•22 years ago
|
||
Confirming, I am getting the same issue sometimes (~~ 1 of 20 attempts to print) ...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•22 years ago
|
||
I am unable to reproduce.
Status: NEW → ASSIGNED
Summary: Status bar for printing does not go away (yet again...) → [REPRO]Status bar for printing does not go away (yet again...)
Target Milestone: --- → mozilla1.0
Comment 4•22 years ago
|
||
I have never seen this (last few months, at least). But I tend to print very simple pages....
Comment 5•22 years ago
|
||
if this can be reproduced pleasse change milestone to 1.0
Priority: -- → P4
Target Milestone: mozilla1.0 → Future
Updated•15 years ago
|
Assignee: rods → nobody
Status: ASSIGNED → NEW
QA Contact: sujay → printing
Comment 6•10 years ago
|
||
hotjobs.com seems to not exist anymore. Please file a new bug if the problem still occurs on other sites. Thanks!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•