- From: szager-chromium <notifications@github.com>
- Date: Thu, 29 Nov 2018 16:08:13 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 30 November 2018 00:08:35 UTC
I want to hopefully close the loop on the comment by @dbaron: > So one thing I need to investigate further is that it feels to me that intersection observer running before the animation frame callbacks seems wrong, I think it should run substantially after them, with a bunch of other stuff in between, since rAF is primarily a writing callback (so should be early, before the natural style/layout), whereas IntersectionObserver is primarily a reading callback (so should be late, after the natural style/layout). You are quite right that IntersectionObserver should run after rAF callbacks; I just created a [pull request](https://github.com/w3c/IntersectionObserver/pull/331l) for that change. The original language there was a mistake. This sidesteps the issue of when exactly style/layout/paint gets updated, but that issue is better addressed in the separate spec issues you called out. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/197#issuecomment-443041161
Received on Friday, 30 November 2018 00:08:35 UTC