- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2023 12:10:35 +0000
- To: public-css-archive@w3.org
Note that one thing I left undefined is the handling of invalid `<font-src>`. Should they be preserved or removed? At parse time? At serialization time?
Chrome/FF (at least) currently remove invalid `<font-src>`, like in `<forgiving-selector-list>` (at parse time, as [specified in step 2](https://drafts.csswg.org/selectors-4/#parse-as-a-forgiving-selector-list)):
```html
<style>
@font-face { src: invalid, local(my-font) }
:is(;, type) {}
</style>
<script>
document.styleSheets[0].cssRules[0].cssText; // '@font-face { src: local(my-font); }'
document.styleSheets[0].cssRules[1].cssText; // ':is(type) { }'
</script>
```
But people now wants to preserve invalid selectors (see issue linked in my first comment).
In `<media-query-list>`, it is more complex because of back-compat.
That said, consistency may not be mandatory.
You may want to specify the current interoperable behavior right now, or wait for the outcome of the corresponding issues for `<forgiving-selector-list>` or `<media-query-list>`.
--
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7632#issuecomment-1757554640 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 October 2023 12:10:37 UTC