- From: Oriol Brufau via GitHub <noreply@w3.org>
- Date: Sat, 27 Dec 2025 20:10:14 +0000
- To: public-css-archive@w3.org
> Remember that the `border-width: 1px` and the `border-style: solid, solid` might be cascading from different sources, each making different assumptions. That's a valid argument. But not a compat argument as previously stated. And I'm not convinced this is the lesser evil. > it means that we can never expose it in whitelists of non-layout affecting properties I'm not sure to which whitelists you are referring to. Do authors use them in some way? Or do you just refer to the internal optimizations in browsers? For the latter, other than the already mentioned case of `border-style: none`, it's fine to only trigger layout damage between some values but not others, several properties do it. So it doesn't seem a big deal to me. Regarding your strawman, it feels a bit overcomplicated to me with multiple properties being able to set the widths. But I will need to think more about it. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13044#issuecomment-3694196617 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 December 2025 20:10:14 UTC