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

[csswg-drafts] [css-tables] track merging

From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
Date: Tue, 13 Sep 2016 22:10:20 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-176763610-1473804618-sysbot+gh@w3.org>
gregwhitworth has just created a new issue for 

== [css-tables] track merging ==
**Compat Issues:** no

CSS 2.1 has very complex rules to decide when or when not to have 
border-spacing between two tracks.
Careful investigation yielded a much simpler way to deal with the 

**Proposed Option:**
Tracks that are not explicitly defined by a table-track box can be 
merged with the previous track for layout purposes if they are spanned
 with same set of cells (plus some minor fine prints for fixed 
layout). This is primarily proposed for spec sanity.

**Here is the proposed text:**
The HTML Table Formatting algorithm sometimes generates more tracks 
than necessary to layout the table properly.

Those tracks have historically been ignored by user agents, so the 
next step just gets rid of them entirely to avoid dealing with them as
 exceptions later in the spec.

**CSS 2.1 Option:** 
Continue to pretend that the HTML algorithm generates an accurate 
representation of the table, and try to emulate previously-exposed 
behavior by cancelling the side-effects of the existence of some 


**Browsers Passing Test:** 
As far as I know, this change is just another way of doing the same 
thing, but it is easier to implement that way.

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

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