- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 17:35:46 +0000
- To: public-css-archive@w3.org
First thoughts: - My gut reaction is that I'm not sure the complexity this adds is warranted by the % of use cases it actually solves (many use cases not solved have already been mentioned above). My personal preference would be to make it easy for authors to dynamically get the metrics needed to craft a reactive expression that resolves to the right radius. - For this to work in the general case (unequal paddings, unequal border widths), it needs to be able to resolve to elliptical radii, so for `border-*-radius` longhands it would need to apply to the whole value. It's unclear how it can be used in the `border-radius` shorthand, since horizontal and vertical radii for the same corner is separated (an unfortunate design decision…). Is it only going to be allowed in the non-slash syntax? -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7707#issuecomment-1755926636 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 17:35:48 UTC