W3C home > Mailing lists > Public > public-web-perf@w3.org > January 2018

Re: Using preload for "async" CSS by changing `rel` trick

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 18 Jan 2018 08:53:54 +0100
Message-ID: <CADnb78g7HVfnBxL+tDGk8Pe7V3Tag5JyMMuHKjbcROPFhOC78Q@mail.gmail.com>
To: Chris Harrelson <chrishtr@chromium.org>
Cc: Ilya Grigorik <igrigorik@google.com>, Ben Maurer <ben.maurer@gmail.com>, Philip Walton <philipwalton@google.com>, Royi Hagigi <royi@fb.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On Wed, Jan 17, 2018 at 7:56 PM, Chris Harrelson <chrishtr@chromium.org> wrote:
> On Wed, Jan 17, 2018 at 2:36 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> Making the load event synchronous just if the style sheet happens to
>> be in a cache seems like a bad API. You effectively change the API
>> contract of <link> based on an externality.
>
> I see, ok. I think you're suggesting that the load event should be async. I
> agree.

Yes, but the thing is that the load event signals when we update the
style sheet list and such too. So if you insert the element and the
frame update happens to happen at the end of that task, you'll miss
the frame.


-- 
https://annevankesteren.nl/
Received on Thursday, 18 January 2018 07:54:39 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 18 January 2018 07:54:40 UTC