- From: Mason Freed <notifications@github.com>
- Date: Thu, 13 Oct 2022 13:29:13 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/issues/1118@github.com>
The CSSWG [recently resolved to add `:open` and `:closed` pseudo classes](https://github.com/w3c/csswg-drafts/issues/7319#issuecomment-1276473056). These will apply to anything that can open/close, which includes `<dialog>`, `<details>`, and `<select>`, and also [the pop-up API](https://open-ui.org/components/popup.research.explainer) (see [DOM](https://github.com/whatwg/dom/pull/1117) and [html](https://github.com/whatwg/html/pull/8221) PRs). For the pop-up API, there is a need for events that fire when these states change. In OpenUI, we [recently discussed the naming for these events](https://github.com/openui/open-ui/issues/607#issuecomment-1278045033), and resolved that we'd prefer to make this a more general set of events that should apply to anything that can be "open"/"closed". For the pop-up API, there is only the need for events that happen **before** the state changes, and interestingly only the "opening" event is cancelable. However, in the general case, it would seem that we should add four events, two for before/after the state changes to "open" and two for "closed". Thoughts? Are there precedents, suggestions, or requirements for the naming of these four events? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1118 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1118@github.com>
Received on Thursday, 13 October 2022 20:29:26 UTC