- From: Aleksandar Totic via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Apr 2021 06:59:16 +0000
- To: public-css-archive@w3.org
I've ran into another place where table painting of collapsed borders does not work: fragmentation. When table is fragmented, headers/footers might be repeated on every page when table is printed. This means that headers will share borders with multiple different tbody rows. I call these cases "fluid grid" cases. "Table paints collapsed borders" assumes that grid is static: cell location is fixed, and table parts do not generate new stacking contexts. But, we have cells that violate these assumptions: - position:fixed cells generate new stacking context, and change location - fragmentation can change cell's location, and neighbor cells. - various css properties can generate new stacking contexts. I think there is a place in the spec for both types of painting. Painting borders by a cell cannot handle some cases: - intersection painting of non-adjacent cell borders, see issue #6039 - painting of column/row borders when cells do not exist. (FF's always done this, TablesNG does it now too). I think that following would be the most powerful solution: - paint all collapsed borders by table - fluid cells also paint their own half-borders, like the spec specifies today. I would like to understand how "self-painting borders" handle intersections. -- GitHub Notification of comment by atotic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3136#issuecomment-823826713 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 April 2021 06:59:18 UTC