- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Sep 2024 12:21:35 +0000
- To: public-css-archive@w3.org
> It's not going to prevent the recalc, but it's going to prevent the changes from being painted. Right, but debouncing to the render steps achieves the same, and happens less often. > Firing it in its own step is also problematic since just like the CSS transition trick, it will inevitably miss changes that will end up painted. I don't understand this point. Can you give a bit more detail on how debouncing this to the render steps would inevitably lead to changes being missed? -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8982#issuecomment-2324626462 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 September 2024 12:21:35 UTC