- From: Gérard Talbot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 May 2019 17:31:52 +0000
- To: public-css-archive@w3.org
Okay. I read the change... but I do not think this makes significant difference with regards to how `orphans` and `widows` can have an effect on line boxes and content distribution among columns. I have replaced `height: auto` with `height: 3.42em` in these 4 tests: [Example 26 without orphans: 1](http://www.gtalbot.org/BrowserBugsSection/CSS3Multi-Columns/column-fill-balance-Example-26-without-orphans1.html) [Example 26 without widows: 1](http://www.gtalbot.org/BrowserBugsSection/CSS3Multi-Columns/column-fill-balance-Example-26-without-widows1.html) [Example 26 without orphans: 1 and without widows: 1](http://www.gtalbot.org/BrowserBugsSection/CSS3Multi-Columns/column-fill-balance-Example-26-without-orphans1-without-widows1.html) [Column-fill: balance Example 26 with 2 line boxes](http://www.gtalbot.org/BrowserBugsSection/CSS3Multi-Columns/column-fill-balance-Example-26-with-2-line-boxes.html) and I still believe Chromium 73+ (and presumably Opera 12.16) handle the first 3 tests correctly, precisely and as expected. - - - - - - Right now, this statement > If columns are balanced, user agents should try to minimize variations in column height, **while honoring** forced breaks, **widows and orphans**, and other properties that may affect column heights. has no examples and no tests. -- GitHub Notification of comment by TalbotG Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3700#issuecomment-497795678 using your GitHub account
Received on Friday, 31 May 2019 17:31:54 UTC