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

I created the issue on the Bikeshed repo because I think it should not generate a link from `<type()>` to `<dfn>type()</dfn>`, which is [documented](https://speced.github.io/bikeshed/#autolink-wrappers)...

  > `<<foo()>>` is an autolink to the function named "foo"

... but is incompatible with:

  > The processor will attempt to infer your definition type from the context and text content of the definition:
  >
  > - [...]
  > - Is it surrounded by `<>`? Then it’s a type.
  > - Does it end with `()`? Then it’s a function.

In my opinion, `webref`/`reffy` do the right thing.

  > `csstree` doesn't make the distinction between a type `<foo()>` and a function `foo()`.

Not all functions are context-insensitive (eg. `minmax()`) and cannot be defined with a production rule like a type.

-- 
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10810#issuecomment-2323465205 using your GitHub account


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

Received on Sunday, 1 September 2024 19:14:05 UTC