(In reply to Oana Arbuzov [:oanaarbuzov] from comment #4) > Both Firefox and Chome, trigger the "Print" preview window That's not what's supposed to happen in Firefox, though. For comparison, try these STR: (1) Load the same doc ( https://docs.google.com/document/d/1jsCkQvHQIikdbouJRYkBF_6-on-e1St9P1sRpX-OsNI/edit ) (2) Wait for the doc to finish loading (give it 10-15 seconds) (3) Ctrl+P This is expected to produce different behavior in Firefox and Chrome right now. In Firefox, it triggers a PDF file to be generated on the server-side and downloaded; whereas in Chrome, it triggers their print preview UI. This difference is expected & intentional for now; see bug 1521655. (Once we've fixed the dependent bugs there, we can ask the gdocs team to give us the same experience as chrome.) But right now, if you perform the additional steps from comment 0, Firefox unexpectedly triggers the print-preview UI. That's the issue here -- Google Docs intends to generate a PDF for us, but in this particular case they do not.
Bug 1693132 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Oana Arbuzov [:oanaarbuzov] from comment #4) > Both Firefox and Chome, trigger the "Print" preview window That's not what's supposed to happen in Firefox, though. For comparison, try these STR: (1) Load the same doc ( https://docs.google.com/document/d/1jsCkQvHQIikdbouJRYkBF_6-on-e1St9P1sRpX-OsNI/edit ) (2) Wait for the doc to finish loading (give it 10-15 seconds) (3) Ctrl+P This is expected to produce different behavior in Firefox and Chrome right now. In Firefox, it triggers a PDF file to be generated on the server-side and downloaded; whereas in Chrome, it triggers their print preview UI. This difference is expected & intentional for now; see bug 1521655. (Once we've fixed the dependent bugs there, we can ask the gdocs team to give us the same experience as chrome.) But right now, if you perform the additional steps from comment 0, Firefox unexpectedly triggers the print-preview UI (i.e. gets the same experience as Chrome, which may produce unexpected issues since we don't yet support some print layout features that google docs relies on). That's the issue here -- Google Docs intends to generate a PDF for us, but in this particular case they do not.
(In reply to Oana Arbuzov [:oanaarbuzov] from comment #4) > Both Firefox and Chome, trigger the "Print" preview window That's not what's supposed to happen in Firefox, though. For comparison, try these STR: (1) Load the same doc ( https://docs.google.com/document/d/1jsCkQvHQIikdbouJRYkBF_6-on-e1St9P1sRpX-OsNI/edit ) (2) Wait for the doc to finish loading (give it 10-15 seconds) (3) Ctrl+P This is expected to produce different behavior in Firefox and Chrome right now. In Firefox, it triggers a PDF file to be generated on the server-side and downloaded; whereas in Chrome, it triggers their print preview UI. This difference is expected & intentional for now; see bug 1521655. (Once we've fixed the dependent bugs there, we can ask the gdocs team to give us the same experience as chrome.) But right now, if you perform the additional steps from comment 0, Firefox unexpectedly triggers the print-preview UI (i.e. gets the same experience as Chrome, which may produce unexpected issues since we don't yet support some print layout features that google docs relies on). That's the issue here -- Google Docs intends to intercept Ctrl-P and generate a PDF for us, but in this particular case they do not.