hello everyone,
i'm currently using FirefoxPortable ESR :102.1.0 customized for my application.
This version of Firefox uses the new print preview user interface which has been introduced in version 86.
In order to switch to the classic System Print Preview dialog box , i have added this preference user_pref("print.prefer_system_dialog", true).
However a problem has occured during the print procedure following these steps:
Click on print
Click on Microsoft Print to PDF
Click on PRINT
then Click on Cancel
the problem is that Firefox is crashing whenver i canceled the print request.
I made an external example to make sure that the problem is not related to my code.
I couldn't solve this issue , could anyone help please !
You are here
Firefox crashes while printing
April 14, 2023 - 9:12am
#1
Firefox crashes while printing
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Are you using 102.1.0 or 102.10.0. The former is unsupported and insecure. The latter is supported for organizations.
Note that if you're altering Firefox/Firefox Portable in any way and redistributing, that's not supported or permitted by Mozilla's license.
Sometimes, the impossible can become possible, if you're awesome!
hello,
I upgraded to firefox portable 102.10.0 but when I added this user_pref("print.prefer_system_dialog", true) preference to display the classic System Print Preview dialog box, a problem occurred when printing following these steps:
Click on print
Click on Microsoft Print to PDF
Click on PRINT
then click on Cancel
The problem is that Firefox is crashing whenever i canceled the print request.
As she said Souha i made an external example to make sure that the problem is not related to my code.
How can I avoid the crush of the application after canceling the print and keeping the classic System Print Preview dialog box? I couldn't solve this issue , could anyone help please !
Unfortunately, this is an issue with the app itself and not something I can assist with.
Sometimes, the impossible can become possible, if you're awesome!