[meta] Support client-side printing in Google Sheets
Categories
(Core :: Printing: Setup, enhancement)
Tracking
()
People
(Reporter: dholbert, Unassigned)
References
Details
(Keywords: meta)
[Spinning this off for followup work from bug 1521655, for one part of gsuite / Google Workspace where our printing behavior hasn't yet changed]
STR:
- Visit some Google Sheets spreadsheet, e.g. this one I just created:
https://docs.google.com/spreadsheets/d/1YNUaOvj8B5HIGKwE_j3B9cJOOtBg9l3BWrUX8TsxriE/edit?usp=sharing - Try to print, using Ctrl+P (or Cmd+P on macOS), or using the in-page "File" menu, "Print" menu-item.
- Click "Next" on the in-page UI that Google Sheets pops up to configure the printed content.
ACTUAL RESULTS:
For now, Google Sheets handles this operation by generating a PDF and opening it in a new tab (which can then be printed if the user does Ctrl+P again).
EXPECTED RESULTS:
Browser's own native print dialog should appear (this is what happens in Chrome). There shouldn't be any PDF involved (unless the user explicitly asks to print to the Save-to-PDF backend).
We should check in with the Google Workspace folks to see what (if any) features/bugs they might be blocked on from us to get this enabled.
|
Reporter | |
Comment 1•1 year ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #0)
We should check in with the Google Workspace folks to see what (if any) features/bugs they might be blocked on from us to get this enabled.
Minor update: I had a brief back-and-forth over email with a contact on the relevant team at Google; they think this is feasible to do, with some work on their side. As far as they know, they're not blocked on us for any features/bugfixes to get this enabled.
|
||
Comment 2•1 year ago
|
||
Should this bug and bug 1917688 be in the Web Compat component instead? It sounds like something Google has to fix in their website not Firefox.
|
|
Reporter | |
Comment 3•1 year ago
•
|
||
That'd be reasonable, but I'm inclined to leave it as-is -- matching the component/categorization of bug 1521655 -- with the intent being to track any Gecko changes that Google folks might uncover later that they need us to fix in order for them to ship.
So: semantically, we're using this as a metabug to track that bucket-of-work, rather than to track the fact that the site itself is broken.
(It's possible the bucket of work is empty and we can close this metabug with no dependencies. That's fine if it turns out that way. But we won't know that for sure until Google's gotten the site to a point where it's working. :) )
Description
•