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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 21 Jun 2013 11:38:29 -0700
Message-ID: <CAAWBYDCUtTbb8hnmGS02t8bC-Z_O0VjTPqN620t218V+4gmDRQ@mail.gmail.com>
To: François REMY <francois.remy.dev@outlook.com>
Cc: Ali Juma <ajuma@chromium.org>, "Robert O'Callahan" <robert@ocallahan.org>, www-style list <www-style@w3.org>
On Fri, Jun 21, 2013 at 11:08 AM, François REMY
<francois.remy.dev@outlook.com> wrote:
>> 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.

Again, read earlier in the thread.  This exact question was raised by
roc, and Ali answered him. I'm not as well qualified to answer this.

Received on Friday, 21 June 2013 18:39:16 UTC

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