[meta] Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content truncated when printing)
Categories
(Core :: Layout: Flexbox, task, P1)
Tracking
()
Webcompat Priority | P1 |
People
(Reporter: dholbert, Unassigned)
References
(Depends on 9 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.
Reporter | ||
Updated•11 years ago
|
Comment 2•11 years ago
|
||
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.
Comment 6•8 years ago
|
||
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
Comment 7•8 years ago
|
||
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
Reporter | ||
Comment 11•7 years ago
|
||
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.
Reporter | ||
Updated•6 years ago
|
Comment 14•6 years ago
|
||
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.
Comment 20•6 years ago
|
||
With the popularity of flexbox, Firefox can't print a sizeable portion of the web.
Updated•6 years ago
|
Comment 24•5 years ago
|
||
bug 1517446 comment 16 points out this also affects https://monitor.firefox.com/
Comment 26•5 years ago
|
||
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.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 38•5 years ago
|
||
I confirm that this bug affects projects like Bootstrap4 and all the projects based on it (e.g. GlobaLeaks) as reported here:
Comment 45•5 years ago
|
||
Reassigning to reflect current ownership.
![]() |
||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 51•4 years ago
|
||
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.
Comment 52•4 years ago
|
||
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...
Comment 53•4 years ago
|
||
(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.
Comment 54•4 years ago
|
||
(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.
Comment 55•4 years ago
|
||
(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
Comment 57•4 years ago
|
||
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
Updated•4 years ago
|
Updated•4 years ago
|
Comment 58•4 years ago
|
||
Unassign myself because this bug turns into a meta bug. That is, development / patches will be in bugs blocking this one.
Comment 59•4 years ago
|
||
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.
Comment 60•4 years ago
|
||
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!
Comment 61•4 years ago
|
||
(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.
![]() |
||
Updated•3 years ago
|
![]() |
||
Updated•3 years ago
|
Reporter | ||
Comment 63•3 years ago
|
||
Given the improvements from bug 1622935, this isn't as severe anymore; we can drop this to S3.
Updated•2 years ago
|
Reporter | ||
Updated•2 years ago
|
Description
•