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

[csswg-drafts] [css-break] table orphans and widows

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Tue, 02 Aug 2016 05:38:46 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-168803579-1470116324-sysbot+gh@w3.org>
frivoal has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-break] table orphans and widows ==
https://drafts.csswg.org/css-break/#widows-orphans

The `orphans` and `widows` properties work fine for textual content, 
but the same concept is needed for tables, so that you can ask for a 
minimum number of table rows that must  be left in a fragment before a
 fragmentation break, or that must be left in a fragment after a 
break.

We could either set up a new pair of properties (table-widows / 
table-orphans), or simply decide that `widows` and `orphans` apply to 
tables as well.

The late seems preferable, since if we had both pair of properties, 
the elements they would apply to would be mutually exclusive. The only
 downside is that it is not entirely clear if inheritance from the 
content surrounding the table to the table, and from the table to the 
table content makes a whole lot of sense.

That could be solved by having `widows` and `orphans` take multiple 
value, the first one applying to lines, the second optional one to 
table rows and defaulting to the same as the first one if omitted. But
 that may be overkill.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/367 using your GitHub 
account
Received on Tuesday, 2 August 2016 05:38:55 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:22 UTC