W3C home > Mailing lists > Public > www-style@w3.org > September 2011

Re: [CSSOM] Revisiting transforms and getBoundingClientRect()

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 8 Sep 2011 14:02:07 +1200
Message-ID: <CAOp6jLad=jeF2+0kay9OcKfULH25AhDsnrHbcVBNs9rZH5dGfg@mail.gmail.com>
To: Erik Arvidsson <arv@chromium.org>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Andrew Dupont <w3@andrewdupont.net>, www-style@w3.org
On Thu, Sep 8, 2011 at 4:55 AM, Erik Arvidsson <arv@chromium.org> wrote:

> Another thing that keeps coming up is to do these things async
> (preferably with deferred/promises) so that we do not trigger
> unexpected layouts. It is not uncommon for code to query the rect just
> to set some style property. If multiple code snippets do this
> consecutively then we get multiple layouts which lead to very slow
> applications.

If the layout changes between requesting the promise and forcing its
evaluation, what should the result be? That sounds hard to spec and likely
to make applications unreliable.

I've always assume applications and libraries should be designed to avoid
excessive layout flushing. What makes that hard?

"If we claim to be without sin, we deceive ourselves and the truth is not in
us. If we confess our sins, he is faithful and just and will forgive us our
sins and purify us from all unrighteousness. If we claim we have not sinned,
we make him out to be a liar and his word is not in us." [1 John 1:8-10]
Received on Thursday, 8 September 2011 02:02:44 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:03 UTC