“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.)
Want to know when I post new content to my blog? It's a simple as registering for free to an RSS aggregator (Feedly, NewsBlur, Inoreader, …) and adding www.ff00aa.com to your feeds (or www.garoo.net if you want to subscribe to all my topics). We don't need newsletters, and we don't need Twitter; RSS still exists.
Legal information: This blog is hosted par OVH, 2 rue Kellermann, 59100 Roubaix, France, www.ovhcloud.com.
Personal data about this blog's readers are not used nor transmitted to third-parties. Comment authors can request their deletion by e-mail.
All contents © the author or quoted under fair use.
