- From: Kevin Doughty via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Jan 2023 17:21:26 +0000
- To: public-css-archive@w3.org
You're right, they can't share a pseudo-element because, yes I propose that removal automatically trigger animation. In fact, I've confused pseudo-classes and pseudo-elements. Implicit element removal animation would need two pseudo-classes, like `view-animation-out` and `view-animation-in`, for selection, and a `children` event handler to sort. A default sort could look for a data attribute like `data-animation-id`. My hope was to piggy-back onto your API and animate out using those pseudo-elements of yours. But I understand now that won't work, if it triggered your API or allowed a redundant way of styling. My experiments with discrete-state suggest that it might be possible to use live elements, and have the browser report discrete destination values only. Sorry for being sloppy, I'll be a lot more precise after implementing it. -- GitHub Notification of comment by KevinDoughty Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8209#issuecomment-1387443052 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 January 2023 17:21:28 UTC