[whatwg] Removal of blocking script
ian at hixie.ch
Wed Feb 9 16:49:38 PST 2011
On Mon, 15 Nov 2010, Juriy Zaytsev wrote:
> When removing  a long-loading script element from a document,
> browsers seem to disagree on whether such removal should affect page
> rendering. A simple test
> http://kangax.github.com/jstests/blocking_script_removal_test/ shows
> that Opera (9.x - 11) and IE (5.5 - 9) immediately continue parsing the
> document upon element removal. However, in Firefox (3-4) and Chrome (9)
> the document parsing is blocked until script is loaded or times out
> (even when the actual element no longer exists in the document, has its
> "src" reference an empty string, and there exist no references to it).
> Does current draft explain what should happen in such case, and if it
> does what is it (I can't seem to find it)? The existing discrepancy
> suggests that it's something worth codifying.
>  Where "removing" is done through scripting (say, via Node's
> `removeChild` or analogous method).
The spec currently implies that the page should block for the full second,
and that the script should still execute.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg