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: Tue, 16 Jan 2018 10:40:57 -0800
Message-ID: <CAOMQ+w-LM0HV6z2ef2thYO9RiJj0rYqohfNNdoLiWicmS9=cHw@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 Tue, Jan 16, 2018 at 2:01 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Sun, Jan 14, 2018 at 9:05 PM, Chris Harrelson <chrishtr@chromium.org>
> wrote:
> > Regarding style sheets: I think the spec / implementations should ensure
> > that "loaded" style sheets always apply to the next frame drawn to the
> > screen.
>
> If you load the style sheet through <link rel=preload> and then
> dynamically insert a <link rel=stylesheet> once the load event
> dispatched on the rel=preload element, I don't think the load event
> should dispatch synchronously on the rel=stylesheet variant and I'm
> not even sure it should/can guarantee that the next frame is hit.
>

Why not? If the DOM is modified, it should apply its updates on the next
frame, no?


>
>
> --
> https://annevankesteren.nl/
>
Received on Tuesday, 16 January 2018 18:41:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 18:41:43 UTC