Re: [w3ctag/design-reviews] Dispatching Toggle Events for Dialog open/close (Issue #1005)

We understand that there was a long discussion that resulted in a single 'toggle' event rather than 'open'/'close' events, 
and don't want to unnecessarily reopen that discussion. However, the platform is currently inconsistent between CSS pseudo-classes, properties, attributes, methods, and events. 
We feel having platform consistency outweighs slight improvements over DX in specific cases here.
If the path forward is a single 'toggle' event, then the CSS pseudo-classes, properties, attributes and methods should be made consistent with that pattern. For example, the pseudo-class values should match the ToggleEvent's `newState` values, which we believe they do. For properties, attributes, and methods, to what extent are they consistent with the 'toggle' pattern?
If the toggle pattern doesn't fit well with the other uses, then it may be time to rethink 'toggle' vs 'open'/'close'.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1005#issuecomment-2576431853
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1005/2576431853@github.com>