[css-grid] problem with page-break-inside: avoid and a 1fr column in CSS Grid
Reported by
jdiet...@gmail.com,
May 31 2016
|
|||||||||||||
Issue descriptionChrome Version : 51.0.2704.63 (Official Build) (64-bit) OS Version: Debian 8.4 What steps will reproduce the problem? 1. Navigate to chrome://flags/ and ensure that "Experimental Web Platform features" is enabled. 2. Open the attached file g.html It has three columns defined: "grid-template-columns: auto 1fr auto;" 3. Type Ctrl-P and look at the print preview What is the expected result? Since the innermost divs (with blue borders) have "page-break-inside: avoid" set on them, I expect that they will not be split across a page boundary. What happens instead of that? Instead, notice that one of the divs--the one in the 1fr column--is split across a page boundary, while the two "auto" columns are bumped to the next page as expected. See the attached file g.png.
,
Jun 1 2016
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.5 using chrome version 51.0.2704.63 and canary 53.0.2753.0. This is regression issue broken in M51.Please find the bisect information as below. Narrow bisect:: good:: 51.0.2703.0 -- (build revision 385938) Bad:: 51.0.2704.0 --- (build revision 386251) CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/61c77cf633505f4a6fe736290522b0c455a85e36..2a193281aac690b3fdfba1246d6b36877553a9be Possible suspect from the above CL https://chromium.googlesource.com/chromium/src/+/52b9bc1b6f112edf95169f9d71fb3b24085df0df jfernandez@ could you please look into this issue if it is related to your change,else please route this to an appropriate dev person. Thanks,
,
Jun 1 2016
Issue 616210 has been merged into this issue.
,
Jun 6 2016
,
Jun 6 2016
,
Jun 7 2016
I'll take a look.
,
Jun 7 2016
It's working fine for me in both 52.0.2743.24 and 53.0.2756.0. Note that Grid Layout doesn't have fragmentation support yet (bug #614667), so the result is not great anyway.
,
Jun 10 2016
@jdietrch could you verify if it's working on Canary?
,
Jun 10 2016
It's working for me on Canary (53.0.2764.0). However, please note: In comment 3, a separate issue I had reported (#616210) was merged into this one. I just checked, and that one is *NOT* fixed on Canary. So I think it's fine to close this issue, but whoever does that needs to undupe/reopen #616210. Thank you!
,
Jun 10 2016
As we said fragmentation is not supported so far, so many of this stuff can be failing. Anyway we just want to confirm it was not a regression, thanks for the feedback. I think we can keep this open and blocking bug #614667, in order to be reviewed once we work on fragmentation. I'll reopen the other bug and do the same, thanks for reporting.
,
Jun 10 2016
,
Jun 12 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 12 2017
,
Jun 13 2017
,
Jun 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 14 2018
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by jdiet...@gmail.com
, May 31 2016