17 September 2009

“WebKit Page Cache I – The Basics”

Since the unload event’s purpose is to allow “important work when a page is closed,” all major browsers refuse to put such pages in their Page Cache, causing a direct negative impact on the user experience.

Interesting: if your page has a <body onunload> (or Javascript equivalent), when the user navigates away from the page, then comes back with the “Back” button, it will be reloaded entirely, and the user will just hate how sluggish his browser is today.

(Which makes sense when you think of it, but something to keep in mind if you have an onunload you don’t quite need. Such as freeing resources for that stupid IE6.)