- From: Byungwoo Lee via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 May 2022 02:38:54 +0000
- To: public-css-archive@w3.org
> Perhaps we should special-case `@supports selector(..)` to not use forgiving parsing?
I think this is a good way to detect the limitations without losing the benefits of forgiving parsing.
Currently, pseudo-elements are explicitly disallowed inside `:is()` (https://drafts.csswg.org/selectors-4/#matches).
If `@supports` can detect the limitation inside logical combinations, I think we can provides more clear limitation in wpt, something like:
```
@supports selector(:is(::first-letter)) {
#supports_first_letter_inside_is { color: red }
}
@supports selector(:has(:host)) {
#supports_host_inside_has { color: red }
}
```
How about others?
--
GitHub Notification of comment by byung-woo
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7280#issuecomment-1128339706 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 May 2022 02:38:55 UTC