Yes.Your conclusion is right. Because Javascript will modify the html structure,i.e,with document.write method.So the html parser need to block when encounter external javascript.But this block would reduce performance. So there's preload scanner. For CSS or other external resources,they have no impact on html document.So they will not influence the parser process.Thus no need for preload scanner.
Date: Thu, 10 Feb 2011 10:02:15 +0530 > From: ROSE-nd-ASH <[email protected]> > To: [email protected] > Subject: [webkit-help] Preload Scanner in WebKit > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > While trying to understand preload scanning in WebKit code, I got to know > that it only starts when HTMLTokenizer encounters JavaScript. Am I right in > concluding so? > If yes why it's not started if we encounters CSS files or other > sub-resources first. Is there any particular reason for this?? > > Thanks for any help. > > Regards, > ROSE-nd-ASH, > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.webkit.org/pipermail/webkit-help/attachments/20110210/c333dc61/attachment-0001.html > > > >
_______________________________________________ webkit-help mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-help
