- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Sep 2016 23:06:30 +0000
- To: public-css-archive@w3.org
gregwhitworth has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-tables] visibility: collapse == **Compat Issues:** yes **Description:** Visiblity:collapse is implemented very differently in various browsers. One outstanding issue is what happens to cells that used to span the erased tracks and are now oversized. **Proposed Options:** Visibility:collapse should act like visibility:hidden when applied to a cell. If all cells in a track are collapsed, the track must get collapsed as though it was set to visibility: collapsed. Based on 2.1 this is a visual change only, so our questions are: **When collapsing and a portion of the cell is visible, what should occur?** A: The cell's contents are clipped (What Safari and Edge currently do) B: The cell's contents overflow (What Gecko does) C: You don't collapse the track since the spanning cell is in the track D: You make this a layout change and you re-layout the cell in the new constraint space **When you collapse a track do you change the size of the table wrapper box?** Currently Gecko/Edge/Webkit all change the size of the wrapper box **CSS 2.1 Option:** Undefined **Testcases:** http://jsbin.com/zodaderama/edit?html,css,output For collapsing of tracks https://jsfiddle.net/fa5q3rf6/ For showing re-layout of the table wrapper box Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/478 using your GitHub account
Received on Tuesday, 13 September 2016 23:06:38 UTC