Re: [csswg-drafts] [selectors-4] Introduce `:popover` pseudo class (#8637)

The CSS Working Group just discussed ``[selectors-4] Introduce `:popover` pseudo class``, and agreed to the following:

* `RESOLVED: Add :popover-open pseudoclass, undefined popoverness from :open`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> chrishtr: we previous resolved to add :open/:closed to apply when popover is opened or closed.<br>
&lt;TabAtkins> chrishtr: &lt;details> has an open/closed concept independent of in the top layer, but it can also be a popover.<br>
&lt;TabAtkins> chrishtr: So we need two axises..<br>
&lt;TabAtkins> chrishtr: Proposal is we scope :open/:closed to an element's own notion of being open or closed. New pseudo :popover that's whether it's in the top layer or not.<br>
&lt;lea> q+<br>
&lt;TabAtkins> plinss: Nit: whether it's "popped over", not necessarily "in the top layer"<br>
&lt;TabAtkins> chrishtr: agreed<br>
&lt;TabAtkins> lea: What does the popover pseudo match, exactly?<br>
&lt;TabAtkins> ???: matches popovers in the open state<br>
&lt;TabAtkins> lea: So what would :popover:closed ever match?<br>
&lt;Rossen_> ack lea<br>
&lt;TabAtkins> chrishtr: A closed &lt;details> element that's popover<br>
&lt;TabAtkins> dbaron: Idea is that it matches popovers who are currently "popover open"<br>
&lt;TabAtkins> dbaron: Open and close are reserved for elements that have their own state.<br>
&lt;fantasai> :pop-open / :pop-closed ?<br>
&lt;Rossen_> ack dbaron<br>
&lt;TabAtkins> lea: I think open/closed is fine, but :popover sounds like it matches any popover element, aka with a popover attribute regardless of whether it's popping or not<br>
&lt;lea> q+<br>
&lt;TabAtkins> Rossen_: So :popover-open sounds like a refinement?<br>
&lt;TabAtkins> chrishtr: Yes, I think :popover-open is descriptive, a little longer but useful<br>
&lt;Rossen_> ack lea<br>
&lt;TabAtkins> lea: I think we had some issues about defining top layer with CSS, want to make sure this doesn't become an obstacle for that<br>
&lt;TabAtkins> plinss: Yes, this just reflects the popover state, not what layer it's in.<br>
&lt;flackr> +1<br>
&lt;chrishtr> +1<br>
&lt;TabAtkins> Rossen_: Seeing +1s in the chat. Can we reoslve to add, with the changed name :popover-open?<br>
&lt;TabAtkins> plinss: Slight hesitancy due to name getting kinda long.<br>
&lt;TabAtkins> plinss: Maybe worth bikeshedding the whole feature name? "popover" is a little weird.<br>
&lt;dbaron> popover is a weird name because calling it popup turned out to not be web-compatible<br>
&lt;TabAtkins> fantasai: Suggest :pop-open<br>
&lt;TabAtkins> dbaron: [reads comment from irc]<br>
&lt;TabAtkins> Rossen_: So :popover-open is proposed resolution<br>
&lt;TabAtkins> RESOLVED: Add :popover-open pseudoclass, undefined popoverness from :open<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8637#issuecomment-1488964330 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 29 March 2023 16:56:30 UTC