2000549 - Documents from "Proton Docs" print with some lines sliced in half at page-breaks

Status: NEW

(Core :: Printing: Output, defect)

Description

[gabriele]

Attachment: Screenshot_2025-11-17-12-23-15-38_99c04817c0de5652397fc8b56c3b3817.jpg

User Agent: Mozilla/5.0 (Android 15; Mobile; rv:138.0) Gecko/138.0 Firefox/138.0

Steps to reproduce:

When I print a multi-page file from Proton Docs, the only way to save it as a PDF is to print the page using Print to PDF. However, Firefox cuts off words if it decides to put them on multiple pages. This does not happen in Opera.

Actual results:

When printing a PDF from Proton Docs, the text is split across two pages and then cut off.

Expected results:

Create a PDF without words being cut off, as happens on Chromium.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:towhite, could you have a look please?

For more information, please visit BugBot documentation.

Comment 3

[Calixte Denizet (:calixte)]

The pdf is created with a pdf printer so the viewer isn't involved here.

Comment 4

[Calixte Denizet (:calixte)]

Attachment: image.png

On windows 11, the print preview in Firefox and Chrome show the same cut text.

Comment 5

[gabriele]

Using the same Proton Docs document, I get two different results between Firefox and Opera on both Windows and Mac.

Comment 6

[Calixte Denizet (:calixte)]

I just tried in Opera with my "Hello World" document and the result is the same as in Firefox and Chrome.

Comment 7

[Daniel Holbert [:dholbert]]

Is there a Proton Docs document that reproduces the issue, that you can share a link to here so we can try to use it to replicate the problem? (It looks like Calixte already tried with a document that he wrote himself, and he wasn't able to reproduce any Firefox-specific badness.)

Or if it's not possible to generate/share a public link with Proton Docs (not sure), maybe you could share steps that reliably result in a "bad" document on your end? (e.g. something like: create a doc, paste in five copies of [some reference paragraph that you're using], select-all, change font size to N, and then print-preview with A4 as the selected paper size)

Comment 8

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #7)

Is there a Proton Docs document that reproduces the issue, that you can share a link to here so we can try to use it to replicate the problem? (It looks like Calixte already tried with a document that he wrote himself, and he wasn't able to reproduce any Firefox-specific badness.)

Or if it's not possible to generate/share a public link with Proton Docs (not sure)

(good news, it looks like it should be possible to generate/share a public link, per https://proton.me/support/drive-share-docs - "To make a document accessible to a wider audience, you can create a public link. This allows anyone with access to the link to view the document.")

So: best way forward here would be for you to craft a doc that reproduces the problem & that you're comfortable sharing, and then we can take a look. Thanks!

Comment 9

[gabriele]

I have enabled you to edit this shared document https://drive.proton.me/urls/NHFEF9TY98#xzKIfbtXR1Q2. The document is divided into two pages, which are perfectly split. With Firefox, the words are cut off.

Comment 10

[Daniel Holbert [:dholbert]]

Thanks. I can confirm the issue in that document.

Using the menu from the filename at the top left and choosing "Print", I get a print-preview dialog in both Firefox and Chrome; and it does appear to split nicely into two pages in Chrome, whereas in Firefox Nightly, some text is sliced at the bottom of page 1 (depending on the exact page size). If I adjust the page margins in Chrome in an attempt to trigger the issue there, a whole line of text moves to the next page, without being sliced.

The difference can be seen more readily if I increase the font size to e.g. 96px (which I did in my own copy of the document, which I created to avoid messing with & depending on the publicly-editable version). Firefox slices text at the bottom of many pages, whereas Chrome only slices footnote-markers (the super-scripts with numeric content like [1]).

If I toggle layout.display-list.improve-fragmentation to false, then the second page is just entirely blank. So we're relying on the "fragmentation fallback" codepath here, and this is a version of bug 1759926.

Comment 11

[gabriele]

Problem still present