- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Feb 2023 18:37:01 +0000
- To: public-css-archive@w3.org
> But more importantly and put more explicitly, I would like to know if desugaring & with :is() implies forgiving parsing for <relative-selector-list>. No, the desugaring with `:is()` is only ever mentioned as an approximation; the spec does not actually use `:is()` for anything internally, and so nothing specific about `:is()` is carried thru. > it is still not clear to me if this resolution with :is() implies that for: As currently written, `::before&` is invalid as the selectors grammar only allows `<pseudo-class-selector>` after it. `::before + &` is valid, as you can put a combinator after a pseudo-element. (It won't match anything in your example, but that's fine.) I'm not sure why your comment says "`::before + :is(span)` is invalid"; it's definitely valid per Selectors grammar. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7503#issuecomment-1433543638 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 February 2023 18:37:06 UTC