- From: <bugzilla@jessica.w3.org>
- Date: Thu, 21 Feb 2013 16:33:56 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21074 --- Comment #3 from Philip Tellis <philip.tellis@gmail.com> --- The timeout has a use case, but I don't think it is a replacement for nonblocking. for example, you may not want to abort the download. you might still want to let it load up whenever it does. Consider a server that generally responds in 50ms, but in 1% of cases takes more than 5 seconds to respond. The user will most likely still be on your page 5 seconds after it starts loading, so the script load will complete, and can still do what it needs to (eg: stats gathering, or a widget at the bottom of the page). Blocking onload for 2 seconds is also not acceptable because we may be blocking execution of scripts for something that really does not care about the onload event. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 21 February 2013 16:33:57 UTC