W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2013

Re: [ResourcePriorities] Blocking content resources on CSS properties

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 6 Nov 2013 11:17:06 -0800
Message-ID: <CAAWBYDCAy-_0B41M65gj5_ghVFUG8=YTcS24VBjpowf1hoF4Qg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Jatinder Mann <jmann@microsoft.com>, Simon Sapin <simon.sapin@exyr.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>, Ivan Kotenkov <kotenkov@yandex-team.ru>, www-style <www-style@w3.org>
On Wed, Nov 6, 2013 at 11:04 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 11/6/13 1:41 PM, Tab Atkins Jr. wrote:
>> Nah, I'm fine with applying it to content resources, with the caveat
>> outlined above that UAs may ignore it and preload anyway during the
>> initial load
>
> I'm not, because this requires UAs to synchronously perform style
> computation after onload in cases when they don't have to do it right now...
> and we don't want to require that sort of thing synchronously. It's
> especially bad in subframes, where style computation means doing a sync
> layout on the ancestor document and all its ancestors because that affects
> media queries which affects style computations...

That's a new argument from what was expressed before, and is quite reasonable.

~TJ
Received on Wednesday, 6 November 2013 19:17:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:37 UTC