Open Bug 1559055 Opened 5 years ago Updated 13 days ago

Fragmented float floats independently of the primary fragment, causing problems while printing

Categories

(Core :: Layout: Columns, task, P3)

68 Branch
task

Tracking

()

People

(Reporter: karlcow, Unassigned)

References

()

Details

(Whiteboard: [layout:print-triage:p2])

Attachments

(1 file)

This is a report produced by RMarkdown with its default template, with the option toc_float: true.

In Firefox, the table of contents box is printed on all pages. On the second page and later, it interferes with text. It should only be printed on the first page.

In Chrome, the table of contents prints at the top of the first page of the report. In Safari, the table of contents prints to the left of text, but only on the first page.

The first page renders correctly when printed from Firefox but on subsequent pages the ToC interferes with text.

It seems they're using position: fixed? If so this should work like it does on Firefox per spec.

So it seems Chrome is not able to float a fragment independently from its primary fragment.

In the test-case above I expect no gap between the two blue boxes.

Sean, do we have a meta-bug for print issues?

Flags: needinfo?(svoisen)
Summary: Floating table of contents is printed on all pages → Fragmented float floats independently of the primary fragment, causing problems while printing
Component: Printing: Output → Layout: Columns

No meta bug for the new project. I'm tagging this as a print triage P2 for now though so we can track it.

Flags: needinfo?(svoisen)
Whiteboard: [layout:print-triage:p2]
Webcompat Priority: revisit → P3
Severity: normal → S3

I can't access the testcase linked in https://webcompat.com/issues/32569 to confirm whether this is still an issue and we don't have any other reports, resetting webcompat priority.

Webcompat Priority: P3 → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: