- From: Aleksandar Totic via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Apr 2021 06:04:09 +0000
- To: public-css-archive@w3.org
We might not be able to completely specify border intersection painting, but I think it would be worthwhile some things can be specified. One example: https://jsfiddle.net/atotic/zLsyh1b9/ ```html <tr> <td border:5px>0,0</td><td>0,1</td> </tr> <tr> <td>1,0</td><td border:40px>1,1</td> </tr> ``` In this example, part of the border of cell 1,1 will be painted inside cell 0,0. This means that part of cell's 0,0 content box will be painted over by a border defined by non-neighboring cell. I think that this cannot be accomplished by painting algorithm currently described by the [standard](https://www.w3.org/TR/css-tables-3/#drawing-collapsed-borders-2). In my understanding the standard specifies that each cell is responsible for painting inside its own border box. But cell 0,0 has no knowledge of the cell1,1's borders, so that cannot be accomplished. As an implementor, I'd really appreciate some guidance from csswg regarding painting of intersections, maybe not "must implement", but at least "this is what we are hoping for". I do not think there are that many issues to sort through. My pet peeve is trying to make dotted borders look good. The problem is that if you paint each border independently, the dots clump at the intersections. Making them overlap gets rid of the clumping, but then you are painting twice over the intersections, which is visible with alpha-transparent colors. Which borders should I prioritize to look good: transparent, or dotted? The issue might be: "Should intersections ever be painted over by more than a single edge?" If the answer is no, what do we do about pattern borders? Discourage their use? Without guidance, intersections are being implemented differently in every browser, which is not great for web developers.  -- GitHub Notification of comment by atotic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6039#issuecomment-823801178 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:04:14 UTC