Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Can You Automatically Revert To DEFAULT Printer Settings Each Print Attempt?

  • 4 risposte
  • 1 ha questo problema
  • 200 visualizzazioni
  • Ultima risposta di Jonathan Watt

more options

Firefox used to revert to default printer settings every time we make an attempt to print. This was ideal for us since we are a business that prints the same style of documents frequently throughout the day, only requiring us to change the settings as needed for one-offs that had different requirements. It was very efficient.

Since the latest update, Firefox "remembers" any changes in printer settings for the next time it prints. So, when we make changes for those one-offs, the next batch of prints are coming out wrong. It is wasting a lot of paper and time.

Is there an option somewhere in Firefox's about:config that turns off Firefox's print settings memory, and forces it to revert to the default printer settings?

Firefox used to revert to default printer settings every time we make an attempt to print. This was ideal for us since we are a business that prints the same style of documents frequently throughout the day, only requiring us to change the settings as needed for one-offs that had different requirements. It was very efficient. Since the latest update, Firefox "remembers" any changes in printer settings for the next time it prints. So, when we make changes for those one-offs, the next batch of prints are coming out wrong. It is wasting a lot of paper and time. Is there an option somewhere in Firefox's about:config that turns off Firefox's print settings memory, and forces it to revert to the default printer settings?

Soluzione scelta

You can try setting `print.save_print_settings` to `false`. You may need to delete all the existing saved settings at the same time of course. (Search in about:config for "print.")

Can I ask, is the printing done on Windows 10?

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (4)

more options

Soluzione scelta

You can try setting `print.save_print_settings` to `false`. You may need to delete all the existing saved settings at the same time of course. (Search in about:config for "print.")

Can I ask, is the printing done on Windows 10?

more options

Also, are you using a Firefox extension/add-on to print, or just printing using the standard File -> Print menu or something similar? I ask because using the latter should always have saved print settings, so I assume you're doing in some other way. If that's true, then some of our latest print changes may have broken things unintentionally. Hence why I'm trying to understand more of the details here.

more options

Jonathan Watt said

You can try setting `print.save_print_settings` to `false`. You may need to delete all the existing saved settings at the same time of course. (Search in about:config for "print.") Can I ask, is the printing done on Windows 10?
Don't know how I missed that setting. It worked. Thanks!

Yes, Windows 10, latest build, up to date.

Jonathan Watt said

Also, are you using a Firefox extension/add-on to print, or just printing using the standard File -> Print menu or something similar? I ask because using the latter should always have saved print settings, so I assume you're doing in some other way. If that's true, then some of our latest print changes may have broken things unintentionally. Hence why I'm trying to understand more of the details here.
Always printing using the standard File -> Print menu. It never previously saved. Maybe someone here previously disabled "print.save_print_settings" to get it working the way we wanted and it went back to TRUE on the latest update.

Fixed now. Will know for next time. Thanks for the fast responses!

more options

Glad your problem is resolved! And thanks for the extra information. That will help for some further digging into what we may have changed here.