- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 Aug 2024 05:48:22 +0000
- To: public-css-archive@w3.org
> Allowing :popover-open to be matched reveals internal implementation details of <select>. In general the less API surface there is, the less problems are likely going to come up in the future. Web APIs should be designed to last. We could decide that popover is no longer the right paradigm for pickers in the future. Should we be stuck with supporting `:popover-open` then? > There shouldn't be more than one way to detect this state in CSS, so we should use select:open instead of ::picker(select):popover-open. Quoting @fantasai: We want form controls to act like they’re built into the language, not built out of author facilities in the language; and that their full functionality can be implemented without those author facilities. `:open` / `:closed` covers the different use cases fine. Should developers care that this is a popover honestly? I think what really matters for the purposes of styling and animation is that it's an element in the top layer. It doesn't really matter if it's a popover or a dialog. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10775#issuecomment-2308141042 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 24 August 2024 05:48:23 UTC