Open Bug 939897 Opened 8 years ago Updated 29 days ago

[meta] Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content truncated when printing)

Categories

(Core :: Layout: Flexbox, task, P1)

task

Tracking

()

People

(Reporter: dholbert, Unassigned)

References

(Depends on 4 open bugs, Blocks 4 open bugs)

Details

(Keywords: meta, Whiteboard: [frag2020][layout:backlog])

Attachments

(2 files)

The current patch stack on bug 811024 lets us split flex containers, but doesn't actually split the children or push any children out of the container's first continuation.

I'm filing this bug on splitting/pushing the children.
Summary: Support shifting / splitting flex items between continuations of the container → Support shifting / splitting flex items between continuations of a fragmented flex container
Blocks: 856235
Depends on: 969147
Depends on: 983427
Duplicate of this bug: 993362
I moved the testcease also. This bug was with the floated div in the past which one is fixed already, so this should be something similar.
Blocks: 1089549
Duplicate of this bug: 1095440
Blocks: 521204
Blocks: 1233125
Duplicate of this bug: 1241323
Duplicate of this bug: 1283642
Walmart is now using display:flex for the main content element on its product pages, so this issue may become more salient. E.g.:

How can I print out this product's warranty information on walmart.com?
https://support.mozilla.org/questions/1130124
Google is now using display:flex on its "printable" directions, so we may start seeing more support questions related to truncated content. E.g.:

When printing maps with directions from Google Maps, I can only print part of the directions.
https://support.mozilla.org/questions/1132728
Blocks: 1288734
Duplicate of this bug: 1331151
Blocks: 1302489
Duplicate of this bug: 1375736
Duplicate of this bug: 1414253
This is likely the reason that bugzilla.mozilla.org itself (e.g. this bug page) is now truncated to one page of output, when printed/print-previewed.
Duplicate of this bug: 1464726
Summary: Support shifting / splitting flex items between continuations of a fragmented flex container → Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content trunctated when printing)
Sorry if this is the wrong place for this comment, but THIS page itself (https://bugzilla.mozilla.org/show_bug.cgi?id=939897) only prints page 1 in firefox now as #wrapper uses display:flex.
Duplicate of this bug: 1486302
Duplicate of this bug: 1486334
Duplicate of this bug: 1489012
Duplicate of this bug: 1493780
Duplicate of this bug: 1123633

With the popularity of flexbox, Firefox can't print a sizeable portion of the web.

Duplicate of this bug: 1549330
Blocks: 1559961
Duplicate of this bug: 1559961
Duplicate of this bug: 1562442
Duplicate of this bug: 1569396

I updated a system's front-end to bootstrap 4 for a company, and they have many long printable pages. They have been using Firefox for the past 8 years because I recommended it to them. Now I have to tell them to move to Chrome because of this bug.

Duplicate of this bug: 193211
Summary: Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content trunctated when printing) → Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content truncated when printing)
Duplicate of this bug: 1579358
Priority: -- → P2
Whiteboard: [layout:backlog]
Duplicate of this bug: 1439156
Duplicate of this bug: 1486289
Blocks: 1315994
Blocks: 1303221
Duplicate of this bug: 1587515
Duplicate of this bug: 1419377
Duplicate of this bug: 1131703
Whiteboard: [layout:backlog] → [layout:backlog][layout:print-triage:p1]
Blocks: 1565186
Duplicate of this bug: 1565186
Duplicate of this bug: 1467240
Duplicate of this bug: 1588204
Duplicate of this bug: 1591953

I confirm that this bug affects projects like Bootstrap4 and all the projects based on it (e.g. GlobaLeaks) as reported here:

Duplicate of this bug: 1597644
Duplicate of this bug: 1599328
Blocks: 1601429
Duplicate of this bug: 1089549
Duplicate of this bug: 1602130
Duplicate of this bug: 1604390
Duplicate of this bug: 1606944

Reassigning to reflect current ownership.

Assignee: dholbert → aethanyc
Whiteboard: [layout:backlog][layout:print-triage:p1] → [layout:backlog:2020q1][layout:print-triage:p1]
Blocks: 1613188
Duplicate of this bug: 1615274
Whiteboard: [layout:backlog:2020q1][layout:print-triage:p1] → [frag2020]
Duplicate of this bug: 1613188
Depends on: 1620490
Depends on: 1622935
Whiteboard: [frag2020] → [frag2020][layout:backlog]
Duplicate of this bug: 1627508
Duplicate of this bug: 1627642
Duplicate of this bug: 1411836
Depends on: 1633028
Depends on: 1633031

This bug collects a lot of duplicates, and can have more before we fix it completely. To reduce the distraction and to break this bug into smaller tasks, I'd like to transform this bug into a meta bug. All the development should happen in the dependencies.

Component: Layout → Layout: Flexbox
Keywords: meta
Summary: Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content truncated when printing) → [meta] Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content truncated when printing)

Printing a page is the most basic/fundamental functionality. Yet, this bug has been 7 years old and still exists in the most recent v75.0. If it doesn't get fixed, there will have more "duplicates" to come, or maybe it's time to move to another browser...

(In reply to ynotswim from comment #52)

Printing a page is the most basic/fundamental functionality. Yet, this bug has been 7 years old and still exists in the most recent v75.0. If it doesn't get fixed, there will have more "duplicates" to come, or maybe it's time to move to another browser...

We are working on fixing this right now. It's one of our highest-priority projects at the moment.

(In reply to Sean Voisen (:svoisen) from comment #53)

(In reply to ynotswim from comment #52)

Printing a page is the most basic/fundamental functionality. Yet, this bug has been 7 years old and still exists in the most recent v75.0. If it doesn't get fixed, there will have more "duplicates" to come, or maybe it's time to move to another browser...

We are working on fixing this right now. It's one of our highest-priority projects at the moment.

Hi,

Since you are working now on this bug that affects printing, please also take a look at bug 1604474, that also affects printing.
On bug 1604474, seems that some of the testcases are duplicates of bug 939897, but there are other testcases (for instance, the doomworld.com testcase) that are not a duplicate of bug 939897.

Like ynotswim said, printing is a fundamental functionality. Every time I want to print a webpage, I have to use Chrome, and this goes on for years now.
Firefox is provided free of charge, and it's my favourite browser since it came out. I'm not complaining about the people that make Firefox, I thank you for all your efforts.

There is also the bug 1201473, that doesn't seem to be a duplicate of bug 939897 and that it seems to affect printing.

Thank you.

(In reply to filipemaia from comment #54)

(In reply to Sean Voisen (:svoisen) from comment #53)

(In reply to ynotswim from comment #52)

Printing a page is the most basic/fundamental functionality. Yet, this bug has been 7 years old and still exists in the most recent v75.0. If it doesn't get fixed, there will have more "duplicates" to come, or maybe it's time to move to another browser...

We are working on fixing this right now. It's one of our highest-priority projects at the moment.

Hi,

Since you are working now on this bug that affects printing, please also take a look at bug 1604474, that also affects printing.
On bug 1604474, seems that some of the testcases are duplicates of bug 939897, but there are other testcases (for instance, the doomworld.com testcase) that are not a duplicate of bug 939897.

Thanks, we will revisit the other testcases on that bug.

Like ynotswim said, printing is a fundamental functionality. Every time I want to print a webpage, I have to use Chrome, and this goes on for years now.
Firefox is provided free of charge, and it's my favourite browser since it came out. I'm not complaining about the people that make Firefox, I thank you for all your efforts.

Agreed, there are various cases where printing in Firefox needs improvement, and over the course of the next several months you should start to see changes for the better. If you want to track the work we are doing that is focused on printing, you can follow this wiki page: https://wiki.mozilla.org/Platform/Layout/Printing_and_fragmentation

Depends on: 1635225
Duplicate of this bug: 1634125

Now that we triage by severity, setting priority to P1 to reflect backlog prioritization on this bug as either in-progress, or planned development in the near term. See https://wiki.mozilla.org/Platform/Layout#Backlog_Tracking_in_Bugzilla

Priority: P2 → P1
Severity: normal → S2
Type: defect → task
No longer blocks: 1613188

Unassign myself because this bug turns into a meta bug. That is, development / patches will be in bugs blocking this one.

Assignee: aethanyc → nobody
Status: ASSIGNED → NEW

Greetings. I'm still having problems in FF 79 with Firefox's inability to render a complete printout of countless webpages. Is this long-standing issue anywhere near being resolved? If it goes on much longer it will be competing with Homer's Odyssey. I went to create a pdf of a webpage this evening, but as usual FF only gave me a 2-page pdf (pages 1 and 17). Once again I had to turn to Safari which provided me with a complete pdf of all 17 pages. If it's necessary for me to attach the 2 pdfs I made which demonstrate the disparity between FF's version and Safari's version I'll be happy to do that. I assume you already have copious examples of webpages that do not print out fully when using FF so I will not attach them here unless they are requested. Please let me know if this issue will ever be resolved or if I should just abandon Firefox and stick with Safari. We Firefox fans are loyal, but this is really pushing it. Thank you.

Re comment 59:

Hi youngjane1118,

It definitely helps if you could file a bug under "Printing: Output" component via https://bugzilla.mozilla.org/enter_bug.cgi?product=Core, and attach the URL of the webpage in the description that Firefox failed to produce the correct pdf. It could help us understand the possible cause and adjust the priority if the same root cause is showing up more frequently. Thanks!

(In reply to youngjane1118@hotmail.com from comment #59)

I went to create a pdf of a webpage this evening, but as usual FF only gave me a 2-page pdf (pages 1 and 17). Once again I had to turn to Safari which provided me with a complete pdf of all 17 pages.

As a temporary workaround, you could try an extension:

  • Print Edit WE: part of the Recommended add-ons program. On its toolbar, look for Tools > Fix Page Breaks.
  • Printable – The Print Doctor: this is my extension and I look forward to it becoming obsolete. Often a click on the first button is all you need to get a printable layout.
Depends on: 1674774
Depends on: park-wta
Depends on: 1677339

Just noticed a similar issue to 1615274 on https://zajno.com/

Depends on: 1695475
You need to log in before you can comment on or make changes to this bug.