- From: davidsgrogan via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jul 2017 02:34:05 +0000
- To: public-css-archive@w3.org
Something came up while Blink was implementing row collapsing. (Which just landed on trunk, should be available in 2017-07-28 canary after enabling "Experimental Web Platform features" in chrome://flags/). https://drafts.csswg.org/css-tables-3/#visibility-collapse-cell-rendering says > If the table-cell is spanning more than one table-track, and the table-track is set to visibility: collapse then **clip the content to the table-cell’s border-box**. If the cell's content overflowed **only** because of visibility:collapse then clipping to the border box makes perfect sense. But if a rowspan cell already has overflow (https://jsfiddle.net/dgrogan/9uduq99L/3/) and then one of the rows it spans is collapsed, the existing overflow also disappears. That's what happens in Edge (modulo the painting bug) and what @joysyu implemented in Blink. Was losing the existing overflow considered? I think it'd be surprising to a web author. -- GitHub Notification of comment by davidsgrogan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/478#issuecomment-318539983 using your GitHub account
Received on Friday, 28 July 2017 02:34:07 UTC