W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2016

[csswg-drafts] [css-tables] What CSS is applicable to table-track & table-track-grouping elements

From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
Date: Tue, 13 Sep 2016 17:27:24 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-176701111-1473787642-sysbot+gh@w3.org>
gregwhitworth has just created a new issue for 

== [css-tables] What CSS is applicable to table-track & 
table-track-grouping elements ==
**Compat Issues:** Yes

Table-rows, Table-row-groups, Table-columns, and Table-column-groups 
are implemented in different ways in each browser. 

**Proposed option:**
The proposal is to have them react to a small set of whitelisted-only 
css properties, describe the expected behavior of those properties, 
and make sure everything else is ignored by the browser. This will 
give browsers more freedom space to accommodate how they deal with 
those internally.

These elements would still generate a box, so you can ask their 
dimension using getBoundingClientRect. Whether table-cells are 
children of those boxes or not is left undefined by the spec, to leave
 more room for implementers.
_Caveat: except in Firefox, table-columns currently do not generate a 

This whitelist currently includes width/height and background. 
Candidate additions would be opacity and transform, which would be 
applied on the cells themselves not on the table-track much like 
background is defined to work which is currently supported in every 
browser but Edge.

Ideally, table-row and table-column to work exactly the same way, to 
bring symmetry into this model. Any property that would make it 
impossible to achieve this goal should not be added to white list.

**CSS 2.1 Option:** 


**Browsers Passing Test:**
NA but the proposal unify quirks of both Blink/Webkit and EdgeHTML
Gecko has issues due to this (see the second testcase), like for 
instance they support position:relative on those elements.

Everyone agrees some things do not work, like overflow:hidden 
(otherwise spanned cells would be problematic).

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/469 using your GitHub 
Received on Tuesday, 13 September 2016 17:27:33 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:03 UTC