- From: <bugzilla@jessica.w3.org>
- Date: Thu, 21 Feb 2013 16:25:33 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21074
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |travil@microsoft.com
--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> ---
Another alternative to simply telling the script not to block the load event,
is to instead allow the developer to specify the timeout value for a script
(since you would have to opt-in to a new attribute 'noblocking' anyway--I
expect that problematic script libraries would need to be known a-priori so
this would work...).
For example:
<script src="script-url" async timout="2s"></script>
Would still block the load event for up to 2 seconds in the worst-case and
would then abort the connection and fire the load event.
Thoughts?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 21 February 2013 16:25:37 UTC