<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 9, 2009, at 4:10 PM, James Robinson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">2009/12/9 tali garsiel <span dir="ltr"><<a href="mailto:t_garsiel@hotmail.com">t_garsiel@hotmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
Well, not completely.<div>Regarding the first question- Webkit guys told me (on their IRC channel) that the don't block the parser and only block scripts that request visual information, so I'm still confused.<br>
</div></div></blockquote><div><br></div><div>Here's my understanding of the implementation inside WebKit currently:</div><div>During parsing, WebKit does not block the parser on stylesheet loads, but does block external scripts from running until previously-encountered stylesheets have loaded. WebKit does not suspend script execution on requests for visual information if stylesheets have not loaded (for example for inline scripts or in the case of stylesheets added dynamically after parsing has completed). WebKit does suspend parsing of the document on script loads, but has a speculative preloader to attempt to start fetches for resources past the <script> tag.</div>
<div><br></div><div>- James</div><div><br></div></div></blockquote><div><br></div>This is accurate, although I'd add that we consider it a bug that we don't yet block the parser for inline scripts in addition to external scripts.</div><div><br></div><div>dave</div><div><br></div></body></html>