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

RE: [ResourcePriorities] lazyload vs. document.readyState

From: Jatinder Mann <jmann@microsoft.com>
Date: Wed, 11 Sep 2013 00:03:25 +0000
To: Ivan Kotenkov <kotenkov@yandex-team.ru>, "public-web-perf@w3.org" <public-web-perf@w3.org>
CC: Константин Никитин <stromsund@yandex-team.ru>
Message-ID: <e2c8750c08274e67a797916a15f7ec76@BLUPR03MB065.namprd03.prod.outlook.com>
Thanks for raising this concern. I think the spec should be clear on the lazyload/postpone impact on document.readyState. I will suggest an updated spec text to address this.


From: Ivan Kotenkov [mailto:kotenkov@yandex-team.ru]
Sent: Friday, September 6, 2013 5:28 AM
To: public-web-perf@w3.org
Cc: Константин Никитин
Subject: [ResourcePriorities] lazyload vs. document.readyState


Document has an attribute readyState which changes during document loading and fires a readystatechange event on it's change.

Current version of the draft doesn't mention this attribute and event, though it is strongly related to window.load event.

My suggestion is to add a subsection about the attribute and corresponding event describing it's behavior when elements with lazyload or postpone attributes exist.

Changing readyState to complete when everything except lazyload\postpone resources is loaded seems intuitive to me, but we can also add another state to document.readyState. Whichever option is better, I believe it should be explicitly stated in the draft.


Ivan Kotenkov
Received on Wednesday, 11 September 2013 00:03:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:01:21 UTC