W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2015

Re: [whatwg] <iframe async>

From: Fady Samuel <fsamuel@chromium.org>
Date: Fri, 27 Feb 2015 10:35:02 -0500
Message-ID: <CAMZzjT=BiQxFSdW0eMp737oDumCidjqPntKjBw02pMp+7vTkNQ@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: WHATWG <whatwg@lists.whatwg.org>, David Bruant <bruant.d@gmail.com>
I've started thinking about "better iframes" lately and I've been thinking
along the lines of async iframes as well. If you start adding iframes
onload, are you not forcing relayout? In an <iframe async> world, you can
compute the layout of the top level frame before beginning to load the
content of the iframe. This seems less jarring (not to mention faster),
because you're not affecting layout of the main page by deferring loading
iframe content?

Fady Samuel

On Fri, Feb 27, 2015 at 10:28 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 2/27/15 10:24 AM, Anne van Kesteren wrote:
>
>> On Fri, Feb 27, 2015 at 4:15 PM, David Bruant <bruant.d@gmail.com> wrote:
>>
>>> To achieve this priorization, currently, authors would use a bit of JS to
>>> delay adding the iframe to the document. It seems like it solves all the
>>> issues listed in the original message (load UI, load event, "fast back").
>>>
>>
>> Delay until what point?
>>
>
> onload, if you don't want it to block onload.
>
> -Boris
>
Received on Friday, 27 February 2015 15:35:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:27 UTC