W3C home > Mailing lists > Public > www-style@w3.org > May 2018

Re: multi-col table layout Fwd: accessible tables

From: Florian Rivoal <florian@rivoal.net>
Date: Thu, 10 May 2018 13:54:15 +0900
Cc: Chaals Nevile <chaals@yandex.ru>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <B0C62DD2-094E-4D28-90A2-A444074CE08C@rivoal.net>
To: Andrew Fedoniouk <andrew.fedoniouk@gmail.com>

> On May 10, 2018, at 1:06, Andrew Fedoniouk <andrew.fedoniouk@gmail.com> wrote:
>> “Now, as for the actual repetition of the table headers:
>> CSS21 says that UAs may repeat them when paginating. css-tables-3 says UA must do so in a very limited set of circumstances (the table is fragmented to pages (as opposed to columns or other things), the repetition wouldn't take more than half the page, the headers / footers have break-inside:avoid applied to them), and that UAs may do so in other circumstances.”
> That may work on read-only media (like printer).
> On others (e.g. screen) it is not clear how UA should handle events on such ghost (a.k.a. synthesized) elements.
> So far CSS is prohibited to generate real DOM elements by its own.

Clearly, this should indeed not be done by generating DOM elements, that is out of what CSS can do.

But since we're talking about a layout effect, these are not elements, they are boxes or fragments. We could say that they they are generate by pseudo elements like ::before or ::after, but that does not seem necessary.  There is a corresponding element in the tree, so we can just solve this by pointing out that this element generates multiple boxes or fragments. Events would map back to the original element. While we are defining the effects of this other than just layout, we should probably also say something about the effect this has (if any) on accessibility mappings.

Received on Thursday, 10 May 2018 04:54:49 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 10 May 2018 04:54:49 UTC