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

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

From: Chris Harrelson <chrishtr@chromium.org>
Date: Wed, 17 Jan 2018 10:56:00 -0800
Message-ID: <CAOMQ+w9RXPd2kHcwxwFCMSB0wAt5XNU-pP=LD_ou12FZbvfS8g@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
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 2:36 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Jan 16, 2018 at 7:40 PM, Chris Harrelson <chrishtr@chromium.org>
> wrote:
> > Why not? If the DOM is modified, it should apply its updates on the next
> > frame, no?
>
> 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.


>
> Furthermore, it would introduce all the problems we're trying to get
> rid of by removing synchronous mutation events (at least all of the
> problems related to synchronous insertion mutation events).
>
>
> --
> https://annevankesteren.nl/
>
Received on Wednesday, 17 January 2018 18:56:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 17 January 2018 18:56:50 UTC