I also notice that the usage is pretty high (according to ), though I'm not sure the number is due to raw uses or through some CSS framework which implement/use it. Plus, the spec is in CR already ( ), so I agree this is something we need to fix. Yeah, as the implementation status from: shows, all other major vendors are supporting this except us. Maybe a distinct, separate bug report should be created and then make it block bug 549114. > That might be implementable separately from the page-break controls. This explains the difference of rendering of 'column-fill: auto' of topmost orange rectangle (with only single alphabetical letters) of this test: Opera 12.16 and Chrome 54+ implement widows (and, presumably, also orphans) for column boxes while Firefox 52.0a1 does not. The CSS3 multicolumn spec uses a SHOULD in such context.Ī page/column/region break opportunity between line boxes is under the influence of the containing block’s break-inside, widows, and orphans properties.ĬSS Fragmentation 3, section 3. In any case, the user agent should try to honor the ‘widows’ and ‘orphans’ properties. > Orphan and widow control is also supposed to apply to individual columns in (In reply to Zack Weinberg (:zwol) from comment #12)
0 Comments
Leave a Reply. |