237632 - pARTNER PDF

Status: RESOLVED EXPIRED

(Core :: Printing: Output, defect)

Description

[satyam]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
Build Identifier: PartnerNET PDF

We have received more detailed answers regarding print problem;
The PDF problem is intermittent 
The error is happening on the Print button  
The PDF Damaged error message comes up about 2-3 seconds later 
Will print second time OK if click on Print again after closing error message 
They are using adobe 6.0 
Appears there is still a problem with Print button being active when file is not
available to print. Please investigate logic to see where this maybe occurring.


Reproducible: Always
Steps to Reproduce:
We have received more detailed answers regarding print problem;
The PDF problem is intermittent 
The error is happening on the Print button  
The PDF Damaged error message comes up about 2-3 seconds later 
Will print second time OK if click on Print again after closing error message 
They are using adobe 6.0 
Appears there is still a problem with Print button being active when file is not
available to print. Please investigate logic to see where this maybe occurring.




Expected Results:  

Should wait till EOF and product PDF

We have received more detailed answers regarding print problem;
The PDF problem is intermittent 
The error is happening on the Print button  
The PDF Damaged error message comes up about 2-3 seconds later 
Will print second time OK if click on Print again after closing error message 
They are using adobe 6.0 
Appears there is still a problem with Print button being active when file is not
available to print. Please investigate logic to see where this maybe occurring.

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

ok... so... why is this marked security-sensitive?

Does this happen in a browser? Which one, and which version?
Which Print button is used, the one from the PDF plugin or the one in the browser?

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

You're using a browser that's over two years old.  Please test in a much more
recent version before filing bug reports.

Comment 3

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Does not seem to be a security-sensitive bug, removing flag.

Reporter, please test with the latest (currently 1.7b) Mozilla browser and
report back here whether you still see the problem or not.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.