[Needs Google fix] Google Docs native print output produces rasterized/unselectable text
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(Not tracked)
People
(Reporter: dholbert, Unassigned)
References
Details
Attachments
(4 files)
STR:
- Be using a Google account that's opted in to the "native" print flow (which requires manual action from some Google folks for now), or using UA spoofing to pretend you're Chrome.
- Load a Google Doc with some text.
- Ctrl+P
(Hopefully this triggers a print-preview popup. If it doesn't, go back to step 1.) - Click through Firefox's print UI to choose the "Save to PDF" print target and go ahead and save it.
- Load the resulting PDF in a PDF viewer, and try to select the text, and try to zoom in.
ACTUAL RESULTS:
The text is unselectable, and it doesn't zoom crisply. It seems to just be a rasterized image.
EXPECTED RESULTS:
Selectable text that zooms crisply.
|
Reporter | |
Comment 1•2 years ago
|
||
Here's an example Google Doc testcase:
https://docs.google.com/document/d/1wKlDGKPJ2VdDQRluT4As4_oKl7WN82gRR_YMuhlH1oE/edit?usp=sharing
|
|
Reporter | |
Comment 2•2 years ago
|
||
|
|
Reporter | |
Comment 3•2 years ago
|
||
|
|
Reporter | |
Comment 4•2 years ago
•
|
||
Here's the PDF that you get if you skip step 1, i.e. from just doing Ctrl+P when viewing the Google Docs testcase and saving the resulting server-side-generated PDF.
|
|
Reporter | |
Comment 5•2 years ago
|
||
Here's a simple testcase taken from MDN with a canvas that has some text drawn onto it.
This works just the same in Chrome and Firefox, and it produces unselectable/rasterized text.
|
||
Comment 6•2 years ago
|
||
Google have a fix for this using mozPrintCallback incoming in the coming week or so. We'll need to retest then.
|
|
||
Comment 7•2 years ago
|
||
The document linked in comment 1 is working now, and other other more complicated documents like this one also seem to be working. (There is some clipping at the left edge of some text in that one, but that would be a separate bug.)
Daniel, any objections to closing this? I'm pretty sure we don't have a way to test for strings in PDFs currently. :-/
|
|
Reporter | |
Comment 8•2 years ago
•
|
||
(In reply to Jonathan Watt [:jwatt] from comment #7)
The document linked in comment 1 is working now
Verified working for me too.
and other other more complicated documents like this one also seem to be working. (There is some clipping at the left edge of some text in that one, but that would be a separate bug.)
Your "more complicated document" URL may've been a mispaste there -- right now it's the same link as in comment 1.
Could you file a bug for the clipping that you're seeing with whatever-that-document-is, if that's not already filed?
Daniel, any objections to closing this? I'm pretty sure we don't have a way to test for strings in PDFs currently. :-/
Sure, let's close as a WebCompat bug (i.e. fixed in the site).
(side note: I think we do have ways to test for strings in PDFs; Tobias added that in bug 1299848, and it looks like the failure message logging is at https://searchfox.org/mozilla-central/rev/da48f565f70a57ac28862090828fbaa7fd8556f6/layout/tools/reftest/reftest.sys.mjs#2211-2218 . But I'm not sure we can do much with making that into a new automated test here -- at least, not with "real" Google Docs.)
|
|
Reporter | |
Updated•2 years ago
|
|
|
||
Comment 9•1 year ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #8)
(In reply to Jonathan Watt [:jwatt] from comment #7)
and other other more complicated documents like this one also seem to be working. (There is some clipping at the left edge of some text in that one, but that would be a separate bug.)
Your "more complicated document" URL may've been a mispaste there -- right now it's the same link as in comment 1.
Could you file a bug for the clipping that you're seeing with whatever-that-document-is, if that's not already filed?
Unfortunately I've not been able to figure out which one I was referring to there. :-/
Description
•