You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the justification for having both of them: #7319 (comment)
Should we also talk about adding the corresponding :closed pseudo class? That would avoid the problem that :not(:open) can match anything, including things that don't open or close.
Note in particular that the justification for :closed is no longer valid with the current HTML PR. We did not want to make :closed only match things that can be closed as this set of items might change over time.
Okay, if you purposely don't want to hook :closed to the "openability" of an element, then yeah, it's completely redundant with :not(:open) and we probably shouldn't add it.
It was resolved here to have both :open and :closed pseudo-classes: #7319 (comment)
@annevk mentioned here that :closed is redundant with :not(:open): WebKit/standards-positions#413 (comment)
Here is the justification for having both of them: #7319 (comment)
The HTML spec has not been merged yet: whatwg/html#10126
The text was updated successfully, but these errors were encountered: