Firefox 86 print preview does not work
Categories
(Toolkit :: Printing, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox88 | --- | verified |
People
(Reporter: zdnexnet, Assigned: evilpies, NeedInfo)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
- Install firefox 85/86 on linux (ubuntu 18.04)
- open any page
- click hamburger menu > print preview
- wait for print (old version was immediate 1sec)
Actual results:
Waiting several hours and nothing printed and previewed. Still loading dialog and Preparing preview.... :(
Expected results:
It should show print in 1 sec as this happened in previus version (ESR 78 or 84?)
|
||
Updated•4 years ago
|
How this can be fixed? Currently I cannot print on this new version of Firefox. This is bad as I was just showing one that Firefox can be viable option, but then we had to print something and I was not able. Was this expected for new version, that some users will not be able to print?
Hi
I have then same issues (bug 1694844).
I think that in my case it is caused by not having a printer installed (I use Print to PDF file).
The Browser console shows this exception error:
Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIPrinterList.systemDefaultPrinterName]
I have several printers and also default printer set. So I guess it is either different bug or it is not connected to printer itself.
|
Assignee | |
Comment 4•4 years ago
|
||
Can you open the browser console and see if there any relevant errors? I would suggest the following
- hamburger menu > web developer > browser console
- clear all messages by clicking on the trash bin in the top left
- Try to print any page
- Go back to the console
This is error what is created. But as I have said I was normally printing before and also in ESR version it works normally.
Uncaught (in promise) TypeError: paper is undefined getMarginPresets chrome://global/content/print.js:958
getMarginPresets chrome://global/content/print.js:986
get chrome://global/content/print.js:1310
updateSettings chrome://global/content/print.js:673
init chrome://global/content/print.js:321
async* chrome://global/content/print.js:91
EventListener.handleEvent* chrome://global/content/print.js:88
|
|
Assignee | |
Comment 6•4 years ago
|
||
Should getMarginPresets handle paper being undefined ? i.e. by using paper?.unwriteableMarginTop. We end up here via getMarginPresets("default", paper), so we should fallback to the defaultSettings anyway.
|
||
Comment 7•4 years ago
|
||
If I try to print a page that is behind basic authentication, Firefox prompts for my login credentials again, then closes the print preview window. The print button will then be unresponsive unless I restart Firefox.
Well I guess that is different problem as this bug is about printing on all pages. Not ones behind auth request.
Btw I guess the system for print should be set same way as it was before, when it was normally working, right?
(In reply to Tom Schuster [:evilpie] from comment #6)
Should getMarginPresets handle paper being
undefined? i.e. by usingpaper?.unwriteableMarginTop. We end up here viagetMarginPresets("default", paper), so we should fallback to the defaultSettings anyway.
Yeah I've run into this in another bug. Handling undefined paper is probably a good idea. Although an undefined paper object isn't expected and might be a indication of another bug upstream, its true that we don't strictly need the paper object to produce those margin values.
(In reply to mackilvane from comment #7)
If I try to print a page that is behind basic authentication, Firefox prompts for my login credentials again, then closes the print preview window. The print button will then be unresponsive unless I restart Firefox.
Could you file this as its own separate bug? It sounds like something we should look into, but its going to get lost posted as comment here.
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 11•4 years ago
|
||
I prepared a build with a fix for this. zdnex would you mind trying if this works for you? Otherwise we probably have to dig deeper into the root of the problem.
https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/TXKGGADpSte9oyDFSTv4SQ/runs/0/artifacts/public/build/target.tar.bz2
Source: https://treeherder.mozilla.org/jobs?repo=try&revision=0fd3f40bb0a516766bf53eb7efafdcc01ad5feba&selectedTaskRun=TXKGGADpSte9oyDFSTv4SQ.0
|
|
Assignee | |
Updated•4 years ago
|
|
Reporter | |
Comment 12•4 years ago
|
||
ok, this seems to work, but I am not sure how to properly test it as I had to use empty profile with just imported prefs. Then print preview opened. I did not try print itself. Anyway I guess I will have to copy profile and try it with that to see how it behaves.
|
|
Assignee | |
Comment 13•4 years ago
|
||
Thanks for checking it out! Does this problem not reproduce on Firefox 86 with a new profile?
|
|
Reporter | |
Comment 14•4 years ago
|
||
On new profile in 86 when I put print it first starts with previus preview (old one) which works and then when I do it again it shows new but again does not finish preview itself and in console it shows same error.
|
|
Assignee | |
Comment 15•4 years ago
|
||
|
|
Assignee | |
Updated•4 years ago
|
|
|
Reporter | |
Comment 16•4 years ago
|
||
So can this fix be included in Firefox release? As currently I was trying to change the printing on my normal profile and I was not able. Btw can I somehow deactivate new dialog to be able to print or I need to wait for fix?
|
||
Comment 17•4 years ago
|
||
|
||
Comment 18•4 years ago
|
||
| bugherder | ||
|
|
Reporter | |
Comment 19•4 years ago
|
||
Should I test this somehow?
|
|
||
Updated•4 years ago
|
|
||
Comment 20•4 years ago
|
||
(In reply to zdnex from comment #19)
Should I test this somehow?
Hello! Can you please test if the issue is fixed with Firefox 88.0b9 / https://www.mozilla.org/en-US/firefox/channel/desktop/. I tried reproducing the issue on Ubuntu 18.04 following STR from comment 0 but with no luck.
Thank you in advance!
|
|
Reporter | |
Comment 21•4 years ago
|
||
Hello,
i am not sure if it is fixed, but now printing seems to be working.
|
|
||
Comment 22•4 years ago
|
||
Closing this based on comment 21.
Description
•