- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 22:22:56 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-shadow-parts] need definition of which pseudo-classes can follow `::part()` that is sufficient to produce interoperability``, and agreed to the following: * `RESOLVED: disallow :has() :scope :host, :host(), and :host-context()` <details><summary>The full IRC log of that discussion</summary> <dholbert> dbaron: this is now going into the details of the rules for which pseudo-classes are invalid or valid after ::not<br> <dholbert> dbaron: this is important because we're introducing concept of part-like pseudo-elements<br> <dholbert> dbaron: this set of rules is now not only applying to part but also to other things<br> <dholbert> dbaron: the spec says the part pseudo element can take pseudo-classes like :hover...tree information... local element information [quoting spec]<br> <dholbert> dbaron: this is a reasonable design guideline for authors, but it's not specific enough to produce interoperability<br> <dholbert> dbaron: some tests revealed differences between implementations on this, RE whether something is tree information vs. local-element information<br> <dholbert> dbaron: what I want to do is change the spec so that it's explicitly listing which pseudo-classes are & are not allowed<br> <dholbert> dbaron: still giving design principle behind that, but making it more explicit<br> <dbaron> https://github.com/w3c/csswg-drafts/issues/10787#issuecomment-2332414419<br> <dholbert> dbaron: proposal is what's in Tab's comment from 3 weeks ago^<br> <dholbert> dbaron: which is basically, the things that we'll disallow the things the spec defines as structural pseudo-classes - first-child, nth-*, etc<br> <dholbert> dbaron: you can't use :has, it's asking about descendants<br> <dholbert> dbaron: you can't use :scope, :host, :host-context<br> <dholbert> dbaron: but all the other current pseudo-classes would be allowed. We'd be allowing :lang and :dir (previuos resolution)<br> <dholbert> dbaron: we'd be allowing :focus-within and :target-within, and :picture-in-picture<br> <emilio> q+<br> <dholbert> dbaron: those are the ones Tab thought were somewhat ambiguous but probably allow<br> <dholbert> dbaron: that's the proposal unless people want to change it<br> <dholbert> emilio: I agree on making it more explicit<br> <Rossen6> ack emilio<br> <dholbert> emilio: I think there are some tests that are invalid, e.g. the last one uses :is ...<br> <dholbert> emilio: I think some of the tests that you landed may need tweaks. I think current behavior from WebKit and Gecko is correct, on :is:first-child etc<br> <dholbert> emilio: because it was resolved that we'd preserve the inner element serialization [?]<br> <dholbert> dbaron: there are some tests that Chromium fails due to serialization<br> <dholbert> emilio: we can sort this out async. generally I support this<br> <dholbert> s/this/the test failures/<br> <dholbert> Rossen6: did you get a chance to check WHATWG discussions to be sure nothing needs to change<br> <dholbert> dbaron: I read through the more recent discussions. I don't think any of that would change this list<br> <dholbert> PROPOSED RESOLUTION: Tab's comment from 3 weeks ago https://github.com/w3c/csswg-drafts/issues/10787#issuecomment-2332414419<br> <dholbert> PROPOSED RESOLUTION: disallow<br> <dholbert> :has()<br> <dholbert> :scope<br> <dholbert> :host, :host(), and :host-context()<br> <fantasai> +1<br> <dholbert> RESOLVED: disallow :has() :scope :host, :host(), and :host-context()<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10787#issuecomment-2380227278 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 September 2024 22:22:57 UTC