W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2019

[csswg-drafts] make break-inside behavior explicit for table elements suck as <tbody> (#4536)

From: Offbeatmammal via GitHub <sysbot+gh@w3.org>
Date: Sun, 24 Nov 2019 22:54:54 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-527771440-1574636093-sysbot+gh@w3.org>
Offbeatmammal has just created a new issue for https://github.com/w3c/csswg-drafts:

== make break-inside behavior explicit for table elements suck as <tbody> ==
http://www.w3.org/TR/CSS21/page.html#page-break-props

Currently:

> User Agents must apply these properties to block-level elements in the normal flow of the root element. User agents may also apply these properties to other elements, e.g., 'table-row' elements

Although, the specs say that user agents may also apply these properties on elements such as tbody, the word "may" plays its role and the behaviour is not uniform across implementations. This creates some sub-optimal experiences as in order to correctly paginate a table at the tbody element (so headers repeat as expected) the workaround is to add a display:block or display:inline-table style which in turn resets a number of other formatting rules.

See https://stackoverflow.com/questions/27753255/page-break-not-working-with-tbody-issue/27754912#27754912 and https://forum.jsreport.net/topic/1361/page-breaks-in-chrome-pdf-not-appearing-as-expected for examples of why this current behaviour is problematic

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4536 using your GitHub account
Received on Sunday, 24 November 2019 22:54:55 UTC

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