Just to comment on this: I’m using requestAnimationFrame which is fired right before the next paint. I was using setTimeout if measurements were not being requested. That’s now fixed.
I did some tests and used the Chrome profiling tools to confirm that the paint was in fact happing after requestAnimationFrame fires. So, at least this concern seems to not be an issue. > On Mar 25, 2018, at 10:03 AM, Alex Harui <[email protected]> wrote: > > I thought that the browsers had immediate updates > after the initial screen draw, so a setTimeout to defer measuring and/or > layout will result in stuff showing up on screen in some weird state until > setTimeout finally kicks in.
