W3C home > Mailing lists > Public > www-style@w3.org > June 2013

Re: [css-display]? Compositing, expensive things, and laziness

From: François REMY <francois.remy.dev@outlook.com>
Date: Fri, 21 Jun 2013 20:08:20 +0200
Message-ID: <DUB120-DS2135A6333F6D7DD354E0AEA58F0@phx.gbl>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "Ali Juma" <ajuma@chromium.org>, "Robert O'Callahan" <robert@ocallahan.org>, "www-style list" <www-style@w3.org>
> Read earlier in the thread - rAF doesn't quite have the right
> semantics for this.

Why? Just before displaying the element (aka switching its opacity from 0 to 
ε), you can register rAF on it, and it will only be called after the element 
has been rendered (at wich point you can start your fading animation). 
You're not forced to call rAF() again to continue being informed of changes. 
Received on Friday, 21 June 2013 18:08:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:12 UTC