- From: Fabio Spampinato via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2023 17:01:43 +0000
- To: public-css-archive@w3.org
> some longhands like border-top-width compute to a length instead of to a color. Of course using a length there wouldn't be valid syntax, but in general we could get ambiguous situations. So how do we know inherit() should be treated as a <color>? I'm thinking `inherit()` could be wired up with all the situations where it would work unambiguously manually. So for example: - `border-top-color`: it gets the `border-top-color` on the parent. - `border` -> it gets the `border-color`, if there isn't one `transparent` or something else could be returned (the average of all the colors on all sides?). - `border-top-width`: this property is not associated with a color, so using `inherit()` here would simply return some fallback value I suppose. Basically I'm thinking a logic that should work would be this: - Is the user calling `inherit()` (or simply `inherit`) inside `color-mix`? If so we are going to get a color. If the user called it for a property where it makes sense it will get the obvious color value for that property on the parent, otherwise something like `transparent`, if not even a non-color to break the `color-mix` call, could be returned. -- GitHub Notification of comment by fabiospampinato Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8872#issuecomment-1574047463 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 June 2023 17:01:45 UTC