User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20090410 SUSE/1.1.16-1.1.2 SeaMonkey/1.1.16 Build Identifier: By mistake I printed a long document instead of the selection I wanted to print. So I aborted the print as soon as I realized the mistake. Now I cannot print any more (Popup says: "Druckerfehler: Nicht verfübar" (Printer Error: Not available)), and even worse, the page cannot be refreshed (Popup says: "Warnung: Das Dokument kann nicht verändert werden, während es gedruckt wird oder die Druckvorschau angezeigt wird." (Warning: Document cannot be modified while it's printed or print preview is displayed)) Reproducible: Didn't try Steps to Reproduce: 1. Print a longer document (with many images) 2. Abort printing quickly 3. Try the print only a selection of the document, or try to refresh it Actual Results: You cannot print the page any more, nor can you refresh it Expected Results: Printing should work, refreshing should work. There should be a way to override the refresh blocking. Found in Firefox 3.5.2 on Windows/XP SP3. May be present on older versions as well.
Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.
I'm currently using Seamonkey 2.0.10 (Build identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:188.8.131.52) Gecko/20101026 SUSE/2.0.10-0.7.1 SeaMonkey/2.0.10). I tried a test when I had disabled the CUPS printer (to save paper): A lengthy document was aborted during print, and after that the page could be refreshed without problem. So the problem might be fixed.
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.