1
edit
Talk:Firefox3/PRD: Difference between revisions
Jump to navigation
Jump to search
Print Events
(Added: Icon Size and Text to Speach Integration) |
(Print Events) |
||
| Line 492: | Line 492: | ||
Then, please make that new links open right next the parent tab, not in the end of the tabs in a window. Frequently I have to drag and drop the new tab to the position near the parent tab to keep my navigation organized (similar things grouped). | Then, please make that new links open right next the parent tab, not in the end of the tabs in a window. Frequently I have to drag and drop the new tab to the position near the parent tab to keep my navigation organized (similar things grouped). | ||
== Print Events == | |||
The addition in JavaScript of the onbeforeprint and onafterprint events would be very useful. This would allow web developers the flexibility to make page changes specific to a printed web page. Most users do not use printer friendly links, especially less tech savvy users, and they should not be denied the same print specific layouts by using file->print. | |||
I would think these events should fire on: | |||
Shortcut key (control-p) | |||
Click on print button, if on toolbar | |||
File -> Print | |||
The argument could be made that this should be out of the specific web pages' hands. The current non-implementation gives the print functionality via the browser's print operations a what-you-see-is-what-you-get printout. If this requirement is deemed critical for users, I would argue for a configuration setting, either in about:config or the print dialog, to force the print of the page "as-is", defaulted to false. This would simply not fire the onbeforeprint and onafterprint during a print operation. I would think that most or all users would prefer a printer friendly page automatically, and if they insisted on an exact printout, would be willing to discover the setting to do so. | |||
Thank you kindly for consideration in this matter. | |||