Re: [csswg-drafts] [css-conditional-3] Define `<declaration>` (#8795)

Right, sorry:

  1. `<declaration>` still needs to reference `<dfn type="<declaration>">` somewhere
  2. I was wrong about `unknown: 1` or `color: invalid` not matching `<declaration>`

I was wrong because browsers accept `@import 'sheet.css' supports(unknown: 1);` (but do not apply the stylesheet). The difference between *accept* and *support* confuses me in:

  > If a processor does not implement, with a usable level of support, the value given, then it must not accept the declaration or claim support for it.

That said, `(unknown: 1)` or `(color: invalid)` matching `<general-enclosed>` instead of `(<declaration>)` seems sane to me because they do not need to be re-evaluated, similarly as `@media (unknown) {}` never needs to be re-evaluated.

This could be achieved by treating the result of matching `<supports-decl>` (instead of `<declaration>`) as a syntax error when it fails to be parsed against the grammar, similarly as an unknown media feature name or an invalid value according to the media feature value definition, matches `<general-enclosed>` (it is evaluated to `unknown`).

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


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

Received on Thursday, 4 April 2024 07:47:27 UTC