W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2017

[csswg-drafts] Define which subresources block the DOM load event

From: Geoffrey Sneddon via GitHub <sysbot+gh@w3.org>
Date: Wed, 08 Mar 2017 16:31:50 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-212785363-1488990709-sysbot+gh@w3.org>
gsnedders has just created a new issue for https://github.com/w3c/csswg-drafts:

== Define which subresources block the DOM load event ==
Moving this over from <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17011>, given that's apparently appropriate nowadays.

CSS should somewhere (hence the lack of any tagged spec!) define which subresources block the load event; at least when that bug was filed IE, Firefox, and Opera blocked the load event on background images and on web fonts loading (which is therefore related to #1082), Safari and Chrome (and this is pre-fork!) didn't, blocking only on `@import`.

I believe someone claimed recently that Edge matches Safari and Chrome, making Firefox the odd one out.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1088 using your GitHub account
Received on Wednesday, 8 March 2017 16:31:56 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:09 UTC