- From: Raura via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Nov 2024 20:57:31 +0000
- To: public-css-archive@w3.org
This is an odd decision, as the current spec defines these state pseudo-classes as only applying to elements where it makes sense to do so. > The :closed pseudo-class represents an element _that has both “open” and “closed” states_, and which is currently in the closed state. — [Selectors](https://drafts.csswg.org/selectors/#open-state) Keeping the status quo similar to the existing form element pseudo-classes, where there are two opposing pairs for a given set of elements, would be helpful to authors given the frustrating experience of having a single property for both hiding and setting the layout type. With `:closed`, they can set a single hiding rule for all relevant elements, including future ones. With just `:open`, they would have to specify declarations for each element manually, and in browsers where `:open` is not supported, simply specifying `:not(:open)` for the `:closed` target would leave the element completely hidden, whereas specifying `:closed` would simply prevent the element from being hidden in that case. -- GitHub Notification of comment by bleper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11039#issuecomment-2492315627 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 November 2024 20:57:32 UTC