- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jan 2025 15:25:50 +0000
- To: public-css-archive@w3.org
bramus has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-images-4] [css-values-5] [css-mixins] The `type()` function is underspecified == The `type()` function appears in https://drafts.csswg.org/css-values-5/#attr-notation, https://drafts.csswg.org/css-images-4/#funcdef-image-set-type, and https://drafts.csswg.org/css-mixins/#typedef-type without one of these really specifying what exactly it is. You can derive it’s meaning, but there’s no single source of truth describing it as a standalone thing. Can we specify the `type()` function in one spec _(which one)_ and have all three uses point to it? I also noticed it has two slightly different kinds of usage: - In `css-images-4` the argument to `type()` itself is parsed into a mime-type, which the UA uses to check whether it supports the format or not. It does not determine how the ` <image>` of the `[<image-set-option>](https://drafts.csswg.org/css-images-4/#typedef-image-set-option)` should actually be parsed. - In `css-values-5` and `css-mixins` the argument to `type()` is meant to determine how the preceding value should be parsed. Kinda the same, but not exactly. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11468 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 January 2025 15:25:51 UTC