Joey Arhar

> > Quickly looking at the implementation in Chrome, :modal does not match after close() going through the transition. > > ``` > dialog:not([popover])::backdrop, > dialog[popover]:modal::backdrop { > background: rgba(0,...

I pushed some commits for similar fixes for the dialog element, which I learned about and am fixing here: https://bugs.chromium.org/p/chromium/issues/detail?id=1451910

@nt1m What do you think of the current state of this PR? I'd like to get multi-implementer interest

Yeah, we could make the internal pseudoclass a real pseudoclass for authors too. It just didn't seem like an important use case to provide for authors

I see how are are kind of requiring authors to transition overlay, but I'd rather not add even more stuff for authors to include to make the exit animation reasonable....

> Sorry for coming in late, but if the existing pseudoclasses aren't sufficient for UA usage, does that indicate they'll similarly be insufficient for author usage? I'm not sure I...

I created a csswg issue to discuss: https://github.com/w3c/csswg-drafts/issues/9912

> I actually wonder if the UA styles could be transition-property: overlay, overflow, inset, etc. by default, but with the transition-duration set to 0. On the author level, they would...

> Even if design systems currently don't allow for the customization of the background animation, if we don't provide a method for developers to customize it wouldn't that prevent design...

@muan So you're saying that it would be better to do `close=light` rather than `lightclose`?