I’ve read that comment three times and still don’t grok it. :-) It seems the comment mixes lookahead pre-parsing behavior with pre-fetching and pre-rendering behavior. Compare the definitions of pre-fetching and pre-rendering in the Google Chrome documentation that the comment points to: http://code.google.com/chrome/whitepapers/prerender.html
With the definition of the lookahead pre-parser from the IE team: http://blogs.msdn.com/b/ieinternals/archive/2011/07/18/optimal-html-head-ordering-to-avoid-parser-restarts-redownloads-and-improve-performance.aspx The comment also states “A pre-_render_, on the other hand, loads a page and all its content, but keeps it hidden. At the moment, it only happens on Chrome.” That was the biggest clue to me that the person was talking about something different because the IE team has written about their lookahead pre-parser. That said, it wouldn’t be the first time something went over my head. Am I wrong that the comment is talking about something different? -Jason On Feb 7, 2012, at 5:37 AM, Anselm Hannemann wrote: > As far as I understand browsers like Chrome preparse sites where they don't > actually get the DOM but load resources they find in code. So it would be > impossible to say it shouldn't be loaded. > See this comment about it: > http://www.alistapart.com/comments/responsive-images-how-they-almost-worked-and-what-we-need/P40/#41
