- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Apr 2017 19:32:27 +0000
- To: public-css-archive@w3.org
This is the bit that says we should define this: https://html.spec.whatwg.org/#critical-subresources Though, really, I would rather not start a discussion about what is critical or what is not. To keep our model sane and automatically up-to-date, I would argue either that any resource downloaded after applying CSS is a critical sub-resource and must be waited on (which means it must be used somewhere on the page before the load event fires otherwise it won't trigger a download), or that no subresource of css is considered critical if it isn't layout-impacting. Based on Geoffrey's findings, Edge has the latter model (we should also delay for fonts though to be consistent) while Chrome has the former model (every subresource is critical). Chrome's model is maybe easier to implement but it delays consequently the load event, which likely has negative perf implications. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1088#issuecomment-293683488 using your GitHub account
Received on Wednesday, 12 April 2017 19:32:33 UTC