- From: <bugzilla@jessica.w3.org>
- Date: Mon, 25 Feb 2013 09:29:49 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21074 Yoav Weiss <yoav@yoav.ws> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yoav@yoav.ws --- Comment #10 from Yoav Weiss <yoav@yoav.ws> --- I support adding a mechanism that avoids blocking of the "onload" event by scripts, but as Kyle mentioned, this is not the only use-case that is not currently covered by `async` and `defer`. I believe that another use-case can be "Loading scripts after onload" in order to load scripts of some added value, but ones which we don't want to intervene with the page's load time. While this can be easily done using scripts, having a declarative way to do that would be easier & cleaner. Also, in some cases, it avoids the use of inline scripts, which is complicated when using CSP. Yet another use case may be loading of scripts according to `media`, since some scripts may be required only for certain layouts. I suggest to gather up all the use-cases and see if we can solve all of them under a single solution. AFAIK, the list includes: * Loading scripts without blocking onload * Loading scripts, but avoiding their execution * Loading scripts after onload * Loading scripts according to `media` Are there any use-cases I'm missing? Yoav -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 25 February 2013 09:29:52 UTC