- From: <bugzilla@jessica.w3.org>
- Date: Sat, 08 Jan 2011 06:34:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11295 Will Alexander <serverherder+w3c@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |serverherder+w3c@gmail.com --- Comment #14 from Will Alexander <serverherder+w3c@gmail.com> 2011-01-08 06:34:39 UTC --- Kyle mentioned t previously, but I wanted to also note: The spec all ready suggests (and IE implements) a solution to this problem -- begin loading the url upon src assignment, wait until insertion to execute. It's buried somewhere in Step 12 IIRC. This provides a mechanism by which deferred execution can be achieved. Since Ordered execution is just a specific type of dererral, it's handled as well. We've had almost identical functionality using images forever. While it may seem to be, IEs readystate is *not* needed. Notifcation in-flight scripts have finished download, while nice, is not required. Simply create the scripts, assign the src, and use run-of-the-mill onload chaining. Since order will always be preserved, it degrades well in browsers that do not implement. I dont think it should be feature-testable. The browser vendor is presumably aware of the spec's suggestion and chose not to heed. Making it testable encourages attempts to thwart the intended behavior. Wlile the symmetry is naturally appealing, I dont see how this async method can be preferable. A global queue is a natural bottleneck and it doesnt seem right that my options are: 1) serially download or 2) introduce artificial dependencies and risk significant delays. Once "trusted" third-parties start using this "feature," it's value erodes quickly. I have struggled with FF's current behavior and know others do to. Would hate to end up back there when, conceptually, there's an alternative. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 8 January 2011 06:34:42 UTC