User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170302120751 Steps to reproduce: This is a follow-on from Bug 1324064 (see comments 19 & 20). A few weeks ago, I released my add-on Print Edit 17.7 to make it compatible with the fix in Bug 1324064. Shortly afterwards, I received a problem report from a Print Edit user who had encountered an error message: "The selected printer could not be found". This happened when the user was trying to preview a web page before printing to PDF. In this case, with Firefox 52 and later, Print Edit sets the printerName in printSettings to "Print Edit PDF". Investigation has shown that: - if e10s is enabled and printerName is set to "Print Edit PDF", then printPreview succeeds. - if e10s is disabled and printerName is set to "Print Edit PDF", then printPreview FAILS! - if e10s is disabled and printerName is set to "", then printPreview succeeds. Note, print to PDF (as opposed to printPreview) always succeeds with printerName set to "Print Edit PDF", whether or not e10s is enabled. In Print Edit 17.10, I implemented a workaround for this problem with printPreview, by setting printerName to "" if e10s is disabled. To reproduce this problem: - use Firefox 52 or later with e10s disabled - install Print Edit 17.7 - on the Firefox main menu bar, select File > Print Preview - tick the "PDF" checkbox on the print preview toolbar - the message "The selected printer could not be found" will be displayed Actual results: Print preview fails and displays the message: "The selected printer could not be found". Expected results: Print preview should succeed.
status-firefox52: --- → affected
status-firefox53: --- → affected
status-firefox54: --- → affected
status-firefox55: --- → affected
Component: Untriaged → Print Preview
Product: Firefox → Core
Mass wontfix for bugs affecting firefox 52.
status-firefox52: affected → wontfix
WONTFIX since this is non-e10s only, and non-e10s is no longer supported.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.