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

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

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 21 Jun 2013 14:39:51 +1200
Message-ID: <CAOp6jLYmXPNnZvub4VA5nq2Z+KdEQ1+8EhS6PF0y1QJ2q0-cfQ@mail.gmail.com>
To: Ali Juma <ajuma@chromium.org>
Cc: Simon Fraser <smfr@me.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, www-style <www-style@w3.org>, Jon Rimmer <jon.rimmer@gmail.com>, Ian Vollick <vollick@chromium.org>
On Sat, Jun 1, 2013 at 1:57 PM, Ali Juma <ajuma@chromium.org> wrote:

> On Fri, May 31, 2013 at 9:34 PM, Robert O'Callahan <robert@ocallahan.org>wrote:
>
>> Is it important to notify the Web page when "the content is ready"? I
>> thought we were going to do this entirely in the engine?
>>
>
> Without getting such a notification, the page won't know when it's safe to
> remove placeholder content, or to make other changes that depend on the
> expensive content being visible (e.g. the page might want to stop a spinner
> from spinning once the expensive content is visible).
>

How is that going to work, since the event must be processed on the main
thread and therefore could happen arbitrarily late? Placeholder content and
spinning could remain in place for a while after the optional content has
been rendered.

Rob
-- 
Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le
atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa
stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm
aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt
wyeonut thoo mken.o w
Received on Friday, 21 June 2013 02:40:18 UTC

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