4 ms·
Along the same lines, Chrome (maybe just webkit generally) does not fire DOMContentLoaded until external script requests have resolved or timed out, even if the
by gavinpc 13y ago
Along the same lines, Chrome (maybe just webkit generally) does not fire DOMContentLoaded until external script requests have resolved or timed out, even if they are async.
Also, I don't understand why people feel so strongly about reposting this "document.write" method everywhere, which I found in some cases made my page disappear at load time. You can do the same thing using regular DOM methods, and you get more control over the process.
- youngtaff 13y agoI believe the blocking of DCL is expected behaviour for scripts with async attribute http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#attr-script-async http://www.whatwg.org/specs/web-apps/current-work/multipage/... If you insert the script using a script it's execution is delayed until after DCL
- wyuenho 13y agoAlso related, when is the HTML working group going to introduce a timeout attribute?