When I print from my online newspaper app, get an extra print dialog that previews a blank page. How to get rid of this extra dialog?
When I print from Chrome or Brave browsers from our local online newpaper app, I get one print dialog with the item I've asked to print shown in the preview. Perfect. When I print from Firefox I get the same thing, but on top of that is another print dialog previewing a blank page that I have to get rid of before I can get to the actual print dialog I want.
So I have to "cancel" the bogus, top dialog that wants to print a blank page, and then the print dialog that I want is available.
Obviously I want to get rid of the first print dialog that wants to print a blank page.
I've gone through the Mozilla "Fix printing problems in Firefox" page, which includes taking all statements with arguments starting with "print_" out of prefs.js in my profile, and that didn't help at all. Exactly the same extra print dialog after doing that.
So I really have no idea why Firefox is doing this when I ask it to print, any ideas how to troubleshoot or fix?
Thanks!
由MrDoh于
所有回复 (3)
Can you provide a link to a page where you have this problem, assuming it is a public page that doesn't require an account to view.
For printing, are you using a button provided by the site, or one of Firefox's built-in methods, such as:
- "3-bar" menu button > Print
- (menu bar) File > Print Preview or File > Print
- Ctrl+p
It isn't a public page, it's an app that you have to pay to use (an online version of our local newspaper). The print button is provided by the app, but I find that Chrome/Brave and Safari both do the right thing when the "Print" icon is clicked, they bring up only the print dialog box that I'm expecting. Only Firefox puts up a bogus print dialog for a blank page on top of the real print dialog.
Not sure how I can get at what the problem might be...I guess I might be stuck with cancelling the bogus print dialog on a regular basis :-), since I do print 2 or 3 things out of the paper every day. Having just shifted over from the Brave browser, not anxious to go back there just for this.
Thanks.
Perhaps they didn't test their script sufficiently in Firefox. You could bring the problem to their attention and see whether they can resolve it.