Bugzilla

(In reply to Václav Trpišovský from comment #10)
> Is there a workaround short of keeping FF<97 or modifying the new browser’s source code to reimplement this preference, both of which cause security issues due to update neglection which I will be happily living with, keeping the print dialog I want by default?

Yes, there soon will be a workaround -- there's work underway to provide an option that jumps straight to the system print dialog (similar to what `print.tab_modal.enabled=false` experience).

> Proprietary software forcing arbitrary UI changes on users is one of the main reasons why many people choose open source. Based on the number of online guides and forum Q&A’s that called to disable `tab_modal` by default, I guess that the option had a reason to stay. You are digging your own grave.

First, I feel obligated to say: I understand you're frustrated, but please tone it down a bit and try to keep comments constructive.  Comments like "You are digging your own grave" are not helpful; see https://bugzilla.mozilla.org/page.cgi?id=etiquette.html 

(I see your `</rant>` -- Bugzilla is not a place for rants, please.)

Addressing your "why did this happen" underlying question: it may not be obvious, but the about:config pref in question was in fact guarding a whole bunch of old/different code, and we don't have the resources to maintain and support the old codepath and new codepath in perpetuity.  The complexity of maintaining two entirely different printing codepaths alongside each other indefinitely would impose a inordinate maintenance burden.  The pref existed so that Mozilla developers could implement the new codepath incrementally, so that it could be tested on beta and quickly rolled back if needed, etc.

Having said that: it sounds like your main concern is that you want to go straight to the system Print dialog (right?), and we *are* planning on providing the ability to get back the old print dialog (without it being intertwined with our old code that was guarded by the about:config pref); stay tuned.

> I was even considering getting Mozilla’s VPN – despite fully aware it was a repackaged Mullvad – just to support your organisation

Thank you for having considered that.

(In reply to Václav Trpišovský from comment #10)
> Is there a workaround short of keeping FF<97 or modifying the new browser’s source code to reimplement this preference, both of which cause security issues due to update neglection which I will be happily living with, keeping the print dialog I want by default?

Yes, there soon will be a workaround -- there's work underway to provide an option that jumps straight to the system print dialog and bypasses the print-preview (similar to the `print.tab_modal.enabled=false` experience, from a user perspective).

> Proprietary software forcing arbitrary UI changes on users is one of the main reasons why many people choose open source. Based on the number of online guides and forum Q&A’s that called to disable `tab_modal` by default, I guess that the option had a reason to stay. You are digging your own grave.

First, I feel obligated to say: I understand you're frustrated, but please tone it down a bit and try to keep comments constructive.  Comments like "You are digging your own grave" are not helpful; see https://bugzilla.mozilla.org/page.cgi?id=etiquette.html 

(I see your `</rant>` -- Bugzilla is not a place for rants, please.)

Addressing your "why did this happen" underlying question: it may not be obvious, but the about:config pref in question was in fact guarding a whole bunch of old/different code, and we don't have the resources to maintain and support the old codepath and new codepath in perpetuity.  The complexity of maintaining two entirely different printing codepaths alongside each other indefinitely would impose a inordinate maintenance burden.  The pref existed so that Mozilla developers could implement the new codepath incrementally, so that it could be tested on beta and quickly rolled back if needed, etc.

Having said that: it sounds like your main concern is that you want to go straight to the system Print dialog (right?), and we *are* planning on providing the ability to get back the old print dialog (without it being intertwined with our old code that was guarded by the about:config pref); stay tuned.

> I was even considering getting Mozilla’s VPN – despite fully aware it was a repackaged Mullvad – just to support your organisation

Thank you for having considered that.