Closed Bug 1417615 Opened 7 years ago Closed 3 years ago

[Layout] Content truncated when printing a page containing a CSS grid with large row

Categories

(Core :: Printing: Output, defect, P3)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: ashafer, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [layout:print-triage:p1][frag2020])

Attachments

(3 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171112125346 Steps to reproduce: 1. Create/load a page containing a CSS grid with a very large row 2. Print the page Actual results: The large row will be shifted onto its own page in the printed document, and content will be truncated if larger than the page Expected results: Content should be split between pages regardless of its position in the CSS grid (Chrome does this correctly)
Component: Untriaged → Printing: Output
Product: Firefox → Core
Priority: -- → P3
Could you attach a simple testcase that demonstrates the issue?
Flags: needinfo?(ashafer01)
Summary: Content truncated when printing a page containing a CSS grid with large row → [Layout] Content truncated when printing a page containing a CSS grid with large row
Version: 57 Branch → unspecified
Files have been attached including a test case and actual/expected results.
Flags: needinfo?(ashafer01)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [layout:print-triage:p1]
Blocks: 1601429
Whiteboard: [layout:print-triage:p1] → [frag2020]
Whiteboard: [frag2020] → [layout:print-triage:p1][frag2020]

Pocket content, such as this page, appears to suffer from this bug: https://getpocket.com/explore/item/how-to-make-kombucha-tea-at-home?utm_source=pocket-newtab

Bug 1640197 / bug 1665214 should fix this when we enable it.

(In reply to Mats Palmgren (inactive) from comment #15)

Bug 1640197 / bug 1665214 should fix this when we enable it.

Update: this is now indeed fixed via that approach (tall-grid-row content should no longer be truncated/lost at pagebreaks).

Having said that, things still aren't perfect, since we'll potentially end up "slicing" text in half at a pagebreak, and that's not-great; bug 1759926 is filed to track that general problem (though we don't have a great solution for that at this point).

I think we can close this bug as fixed-by bug 1640197 and bug 1665214, though.

Status: NEW → RESOLVED
Closed: 3 years ago
Depends on: 1640197, 1665214
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: