[csswg-drafts] [css-mixins-1] `<type()>` conflicts with a previous definition in `css-images-4` (#10810)

romainmenke has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-mixins-1] `<type()>` conflicts with a previous definition in `css-images-4` ==
`css-images-4` defines: https://drafts.csswg.org/css-images-4/#funcdef-image-set-type

```
<image-set()> = image-set( <image-set-option># )
<image-set-option> = [ <image> | <string> ]
                     [ <resolution> || type(<string>) ]?
```


`css-mixins-1` defines: https://drafts.csswg.org/css-mixins-1/

```
<@function> = @function <function-name> [ ( <function-parameter-list> ) ]?
  [ using ( <function-dependency-list> ) ]?
  [ returns <css-type> ]?
{
  <declaration-rule-list>
}

<function-name> = <dashed-ident>
<function-parameter-list> = <function-parameter>#
<function-dependency-list> = <function-parameter>#
<function-parameter> = <custom-property-name> <css-type>? [ : <declaration-value> ]?
<css-type> = <syntax-component> | <type()>
<type()> = type( <syntax> )
```

These are different and do not overlap in practice because one is only valid in declaration values and the other only in `@function` preludes.

But the conflicting definition makes it harder to extract syntax information from specs.

It is also apparent in the specs itself because `<type()>` in `css-mixins-1` actually links to the definition in `css-images-4`.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10810 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 31 August 2024 15:33:48 UTC