@DavidBruant Do you have an explanation for this Firefox phenomenon?https://twitter.com/rauschma/status/513385559658864640 …
-
-
Replying to @DavidBruant
@DavidBruant@bz_moz Superficially, it looks as if setTimeout() callback is executed synchronously if delay <= DOM_MIN_TIMEOUT_VALUE2 replies 0 retweets 0 likes -
Replying to @rauschma
@rauschma@DavidBruant Nothing is being done sync here in Firefox. Just two async things with different delays, one shorter than the other.2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@DavidBruant Got it, thanks! Is there a way to make sure that what you queue is executed after layout?1 reply 0 retweets 0 likes -
Replying to @rauschma
@rauschma@DavidBruant requestAnimationFrame twice (the first one will run right before the next layout pass; the second one the tick after)1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@DavidBruant Thanks, interesting idea. Twice doesn’t seem to be enough, though: http://rauschma.github.io/2ality-es6-promises/blocking2.html … Any idea why?1 reply 0 retweets 0 likes -
Replying to @rauschma
@rauschma@DavidBruant Not offhand... :( It might have to do with when actual painting, as opposed to layout, happens.2 replies 0 retweets 1 like -
Replying to @really_bz
Axel Rauschmayer Retweeted Axel Rauschmayer
@bz_moz Thanks! I’ve publicly asked how to best do this in a cross-browser manner:https://twitter.com/rauschma/status/514044497681186816 …Axel Rauschmayer added,
1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.