1889252 - Links aren't clickable in Google Doc print-to-PDF output (using native gsuite printing)

Status: RESOLVED DUPLICATE of bug 1892816

(Core :: Printing: Output, defect)

Description

[Daniel Holbert [:dholbert]]

STR:

1. 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.
2. Load a Google Doc that has a link, e.g. this one:
   https://docs.google.com/document/d/16aHywCCQpb5FV43DzFXnWDIWFAvL0U2slJPaeRhiERQ/edit?usp=drive_link
3. Ctrl+P
   (Hopefully this triggers a print-preview popup. If it doesn't, go back to step 1.)
4. Click through Firefox's print UI to choose the "Save to PDF" print target and go ahead and save it.
5. Load the resulting PDF in a PDF viewer, and try to click the link.

ACTUAL RESULTS:
The link isn't clickable/hyperlinked.

EXPECTED RESULTS:
The link should be clickable/hyperlinked.

(This might really be a server-side bug on the Google Docs side, similar to bug 1865200, where they're not doing all the right things to get the link to be clickable in mozPrintCallback; I'm not entirely sure. Possibly worth trying to fix before we get Google Docs native print support shipped -- or as a followup item -- because clickable links in docs can be pretty important, and losing the URL entirely is a form of dataloss that's not immediately obvious but can be quite annoying when you run up against it.)

Comment 1

[Daniel Holbert [:dholbert]]

Attachment: bug: PDF generated from Firefox's print dialog (link isn't clickable)

Comment 2

[Daniel Holbert [:dholbert]]

Attachment: reference: PDF generated server-side by Google Docs (in Firefox, not using native print dialog)

Here's the PDF (with a working clickable link) that's generated by the existing server-side gsuite printing flow that our users get right now.

Comment 3

[Daniel Holbert [:dholbert]]

Attachment: reference: PDF generated by Chrome's print dialog

Comment 4

[Jonathan Watt [:jwatt]]

The patch for bug 1892816 seems to fix this bug too.

Comment 5

[Jonathan Watt [:jwatt]]

Daniel, can we dup this to bug 1892816?

Comment 6

[Daniel Holbert [:dholbert]]

Sure - I confirmed that the STR seem to give the expected results in Nightly 127.0a1 (2024-04-25). Thanks!