- From: Emilio Cobos Álvarez via GitHub <noreply@w3.org>
- Date: Thu, 19 Mar 2026 20:50:01 +0000
- To: public-css-archive@w3.org
No, that comment was meant as "I support defining the shadow tree using existing primitives like popover rather than magic". The behavior Chromium implements falls out of that, which is `select:open` matching and `::picker(select):popover-open` matching as well. But of course the DOM structure of the shadow tree should be properly defined. That includes specifying the tagname and popover attribute value that the picker would have, _and_ defining the UA sheet in a way that actually works, without requiring random internal pseudo-classes. I _could_ live with defining the picker as a magic div that doesn't have a popover attribute and doesn't match `:popover-open` but somehow is a popover, but that seems kinda silly tbh? -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10775#issuecomment-4093211928 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 March 2026 20:50:02 UTC