7896 2009-10-12 09:11:43 +0000 Specify pageshow and pagehide events 2010-10-04 13:55:09 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED FIXED NE P2 normal --- 1 zcorpan ian ian mike mjs public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 28259 0 zcorpan 2009-10-12 09:11:43 +0000 Apparently Gecko and WebKit have implemented pageshow and pagehide events (and onpageshow/onpagehide event handler attributes). http://webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/ I guess this is something that should be specced in HTML5. 28260 1 mjs 2009-10-12 10:00:22 +0000 I agree, this is worth specifying. These events are becoming de-facto necessary to implement a Web-compatible back/forward cache. 28656 2 ian 2009-10-21 06:07:25 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 28657 3 contributor 2009-10-21 06:08:06 +0000 Checked in as WHATWG revision r4231. Check-in comment: Add pageshow and pagehide events. http://html5.org/tools/web-apps-tracker?from=4230&to=4231 28662 4 zcorpan 2009-10-21 06:23:48 +0000 (In reply to comment #1) > I agree, this is worth specifying. These events are becoming de-facto necessary > to implement a Web-compatible back/forward cache. > Maciej, could you check whether the spec matches what is implemented in WebKit, please? 31010 5 zcorpan 2010-01-13 09:24:03 +0000 WebKit and Firefox uses the PageTransitionEvent interface, which has members .persisted and .initPageTransitionEvent(). 31011 6 zcorpan 2010-01-13 09:34:17 +0000 Also, pageshow should have target set to document (just like the load event). 31012 7 zcorpan 2010-01-13 09:37:56 +0000 (In reply to comment #6) > Also, pageshow should have target set to document (just like the load event). > ...and pagehide 31870 8 ian 2010-02-13 01:14:45 +0000 What does .persisted return? 32269 9 zcorpan 2010-02-17 11:55:05 +0000 It returns true for pageshow if the page is loaded by navigating in history and the page was not garbage collected, I think. It always returns true for pagehide, AFAICT. 32566 10 ian 2010-02-23 11:25:29 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 32567 11 contributor 2010-02-23 11:29:26 +0000 Checked in as WHATWG revision r4800. Check-in comment: Make pageshow/pagehide use PageTransitionEvent, to match reality as described by zcorpan. http://html5.org/tools/web-apps-tracker?from=4799&to=4800