- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Oct 2022 13:08:01 +0000
- To: public-css-archive@w3.org
I think 1 is fine. 2 seems leaky, and unlikely to do what the developer wants. For example, say a counter is updated via a websocket. Meanwhile, a transition is 'reversed'. The developer may want to go back to the previous view, but it's unlikely that they'd want the counter to decrement too. DOM caching wouldn't be able to differentiate between the two. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7957#issuecomment-1292008648 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 October 2022 13:08:02 UTC