News for hackers. Stuff that matters.
Re:WebKit and Chrome prerendering by spiralganglion on Sunday June 19, 2011 @10:50PM (#2672653)
This sounded like a potentially useful feature for web developers, to improve perceived loading speed without having to use JS (which may be desirable in some situations). But reading Google's notes on the subject is like a splash of cold water: http://code.google.com/chrome/whitepapers/prerender.html

TL;DR: Only one page may be prerendered at a time per-instance of Chrome (not per-tab).

It would be nice to know if this just limits simultaneous prerendering, or if only one link may be prerendered and it must be clicked on or "evicted" before any more prerendering will occur.

Re:WebKit and Chrome prerendering by eridius on Monday June 20, 2011 @04:33AM (#2673399)
I can't speak definitively, but I doubt the prerendered page needs to be visited before another one can be prerendered. If that were the case, I could open a google search and leave it in a background tab and never ever get prerendering ever again.
Re:WebKit and Chrome prerendering by spiralganglion on Monday June 20, 2011 @04:44AM (#2673417)
Yes, that's what I'm afraid of. It's not clearly stated if that is or isn't the case. Their wording is ambiguous. I'd test this myself using the dev build of Chrome, but I can't install it where I am.

Anyone else?