W3C home > Mailing lists > Public > www-style@w3.org > January 2017

RE: [css-tables] Dropping repeated headers/footers when one content row doesn't fit

From: François REMY <francois.remy.dev@outlook.com>
Date: Fri, 6 Jan 2017 23:36:14 +0000
To: Florian Rivoal <florian@rivoal.net>, Robert Hogan <robhogan@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <AM2PR04MB0818383A1EBD8211F842B32DA5630@AM2PR04MB0818.eurprd04.prod.outlook.com>
Can you please have a look at the new text and tell me if that works for you both?

I didn't call out an explicit algorithm for now but trying to write one informed how I rewrote some of the paragraphs.

https://drafts.csswg.org/css-tables-3/#fragmentation





-----Original Message-----
From: François REMY 
Sent: Friday, January 6, 2017 1:08 PM
To: 'François REMY' <francois.remy.dev@outlook.com>; Robert Hogan <robhogan@gmail.com>; www-style list <www-style@w3.org>
Subject: RE: [css-tables] Dropping repeated headers/footers when one content row doesn't fit

>> I'm reading it to say that as long as repeating the header and footer leaves room for at least part of a tbody row in the fragmentainer then they can both remain. If it doesn't, but dropping the repeated footer allows room for at least part of a tbody row, then drop the repeated footer but keep the repeated header.
>
> Correct that is what browsers seems to do today.

Actually I had a look at our source code, and what Edge and Firefox do is easier than that even, we just repeat the footer/header if they occupy less than 25% of the fragmentainer height. Combined they can therefore never account for more than half of the fragmentainer height, which means that it should be enough to fit a row for sure.

I will put that in the spec, that seems reasonable to me.
Received on Friday, 6 January 2017 23:37:00 UTC

This archive was generated by hypermail 2.3.1 : Friday, 6 January 2017 23:37:01 UTC