[csswg-drafts] [css-syntax-3] Should a declaration value be consumed as a `<declaration-value>`? (#11315)

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

== [css-syntax-3] Should a declaration value be consumed as a `<declaration-value>`? ==
In [consume a declaration](https://drafts.csswg.org/css-syntax-3/#consume-declaration), it is currently consumed as a (unrestricted) list of component values.

But in the current version of Chrome and FF (at least), it seems to be consumed as a [`<declaration-value>`](https://drafts.csswg.org/css-syntax-3/#typedef-declaration-value):

```html
<style>
  style {
    color: var(--color) url(bad url);
    color: var(--color) );
    color: var(--color) !;
  }
</style>
<script>
  document.styleSheets[0].cssRules[0].cssText; // style {}
</script>
```

I could not say whether [CSS2](https://drafts.csswg.org/css2/#tokenization) also considered these declarations as invalid.

CSS Syntax 3 is less restrictive, which can change the declared value:

```html
<p style="color: green; color: var(--opacity) url(bad url);">
  black per spec,
  otherwise green
</p>
```

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


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

Received on Tuesday, 3 December 2024 13:51:17 UTC