- From: Donnie D'Amato via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 15:23:16 +0000
- To: public-css-archive@w3.org
I've thought a lot about how this might exist systematically, I put my thoughts [in this post](https://blog.damato.design/posts/meaningless-curves/). But here's the finer points: - I think it makes sense for the _inner radius_ to be the driver of overall nested rounding for the rest of the page as the inner-most radius should be the smallest amount of rounding we'd want to see. If the parent drives the radius, it's possible we end with no rounding at the deepest levels. This means that smaller elements drive the rounding of larger containers. - This would also mean that the rounding of the outer element would depend on the existence of the smaller element. If we had several similar cards, but only one had a rounded button inside, how would we determine what the rounding of the other cards would be to match? Virtual elements? - Now, if you believe that the outer radius is the driver, this also may cause elements to never receive rounding. You might imagine a straight-cornered navigation bar which expects a rounded button to match the rest of the rounding in the page, but it never receives the rounding values because none of the ancestors are rounded. Ultimately, I think @tabatkins [comment about not addressing all the scenarios](https://github.com/w3c/csswg-drafts/issues/7707#issuecomment-1239842790) is the best path forward. It just means we need to be clear about what this is expected to solve and what it will not. -- GitHub Notification of comment by ddamato Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7707#issuecomment-1755682089 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 15:23:18 UTC