- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jan 2023 04:33:58 +0000
- To: public-css-archive@w3.org
Ok, I only checked the [browser compat table](https://developer.mozilla.org/en-US/docs/Web/CSS/@supports#browser_compatibility). I am fine with unforgiving parsing (minus the observation in my previous comment) but the related note (quoted below) seems a bit handwavy to justify evaluating `selector(:is())` to false: > Note: Some functional selectors are parsed forgivingly, i.e. if some arguments are unknown/invalid, the selector itself is not invalidated. These are nonetheless unsupported Resolving to false means that `:is()` take `<selector-list>` (list cannot be empty) instead of `<forgiving-selector-list>` (list can be empty). I mean, this is not a context rule applying on the result of `<forgiving-selector-list>`, whereas restrictions apply when pseudo-classing a pseudo-element, for example. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8295#issuecomment-1378229630 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 January 2023 04:34:00 UTC