1. https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&comp...
In the case of the new print preview/workflow, however, I expect it will provide virtually everyone with a better workflow once we've finished polishing any rough edges. The feedback on places like Reddit indicates that it's already a very clear net win for most users, and I think we can address most of the complaints on support.mozilla.org etc. The eventual removal of the `print.tab_modal.enabled` preference and the old code will simply be because having two print preview implementations adds code complexity and is a maintenance burden.
I understand that the needs of any one user, such as me, with a particular idiosyncratic set of needs and preferences are at odds with those of the body of users as a whole, who need an appropriate balance between customiseability and useability, together with, of course, deliverability—it's no good having a product custom-tailored to fit every possible combination of needs if the developers collapse under the maintenance weight.
I didn't really mean what I said as anything other than a cri de cœur: it sometimes seems that Firefox rode to its current position on the wave of the love and passion of power users, a group of which I am on the periphery, but now cares more about its numerically larger but less devoted casual user base. This is probably the right decision, but it's still frustrating as one of those long-time users (from back in the Phoenix days!).
I really dislike this philosophy of replacing the system functionality. Particularly on Mac where the system functionality is quite good. (On Windows and Linux, I admittedly don't care as much, because nothing is ever consistent anyway...)