- From: jsnkuhn via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 May 2025 12:01:30 +0000
- To: public-css-archive@w3.org
When I create an element on the web it's default corner shape _is_ square. The heart of the problem here is the shoehorning of `border-radius` into the situation acting as a "corner-size" and "corner-shape" which forces rounded corner "fallbacks" whenever `corner-shape` is used even if that styling is inappropriate/unwanted like with `notch`, `scoop`, `bevel`, or sometimes even `squircle`. An example to illustrate is this page for the upcoming pokemon game (https://www.pokemon.co.jp/ex/legends_z-a/ja/story/). The beveled corners on the `h1` are there to mirror the header background image that includes it's own baked in bevels. A forced `round` fallback for the declared `bevel` would visually contrast with the rest of the page design. This will mean that the dev/designer will have to dance around a poor forced fallback.  I can't think of another situation like this in CSS when a non-default style is forced on developers when a certain property is used. It would be something like if a developer declared an unsupported p3 background color the browser just gives you `red` and pretends that is helpful Or if your background-image doesn't load in the browser were to just give you a `linear-gradient(blue,orange)`. A way around this problem is to create a `corner-size` property to go along with `corner-shape` and then allow devs to use `border-radius` as a fallback if they chose to. -- GitHub Notification of comment by jsnkuhn Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11623#issuecomment-2909489818 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 May 2025 12:01:31 UTC