column-* doens't work properly
Reported by
rodrigo....@betalabs.com.br,
Aug 10 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Example URL: http://www.barradoce.com.br/ Steps to reproduce the problem: 1. Hover a mouse on the menu bar What is the expected behavior? Show 5 columns side by side equals to other browsers What went wrong? column-count and column-width are with misbehavior and do not follow the amount of columns defined Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 52.0.2743.116 Channel: stable OS Version: Flash Version: In chrome 48 works ok
,
Aug 11 2016
Able to reproduce the issue on mac 10.11.5 chrome version 52.0.2743.116 and canary 54.0.2826.0 Please find the screenshot The issue can be seen on win and Linux as well This issue can be seen in M48 build 48.0.2564.108 as well. Please let me know if further bisect is needed on the same
,
Aug 11 2016
,
Aug 12 2016
,
Aug 12 2016
,
Aug 12 2016
Demo for http://www.barradoce.com.br/ attached. Each section in the menu on that site is an inline-block on a line in a multicol container. We cannot break inside lines. That's not allowed. Also, orphans and widows are 2 (initial value), so we should try to put at least two lines (i.e. two sections) in each column. We're doing nothing wrong with that site, as far as I can tell.
,
Aug 12 2016
http://www.jetstar.com/nz/en is the same issue. New Zealand and Australia need to be in the same column, because they each form one line in the multicol container, and orphans/widows are 2.
,
Aug 12 2016
Those are admittedly some tall and weird "lines", but they are still lines, so orphans and widows requirements should be respected in a fragmentation context. Not using inline-blocks for each section would solve the problem. Using regular blocks would make much more sense. If they don't want column breaks inside the blocks, just add "break-inside:avoid". But I suspect that the reason for using inline-block in the first place is that break-avoid has limited support across browsers. So that using inline-block is the only way of preventing undesired column breaks. So maybe just set orphans and widows to 1, and everyone would be happy? Anyway, the undesired rendering here is not caused by a bug in the engine. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by bris...@gmail.com
, Aug 11 201678.4 KB
78.4 KB View Download
85.8 KB
85.8 KB View Download