-
Notifications
You must be signed in to change notification settings - Fork 447
Unload code not called on iPhone/iPad #43
Comments
Still figuring out GIT. Somehow my branch is not 'public' so I cannot see my local checkins on this web-site in order to issue a pull request...? Here's the code I added to boomerang.js. "pagehide" for iPhone/iPad and "onunload" for blackberry....
|
Hi @solarice thanks for the patch. We've moved development to https://github.com/lognormal/boomerang/ I'll merge your changes in there and give you credit. Regarding the change you made for BlackBerry, don't we already listen to the unload event? Or does BlackBerry do something weird with event names? |
Yes, sort of. Exiting code had "unload" but blackberry uses "onunload".
The impl.addListener method adds the "on" prefix when calling "attachEvent", but that's not getting used....
http://docs.blackberry.com/en/developers/deliverables/11848/HTML_ref_event_attributes_600908_11.jsp P.S. Thanks for adding in the iPhone/iPad portion. I'll try syncing up again as there's other fixes/enhancements I'd like to add. |
wouldn't we also need to do this for the onload event in that case? |
That's a good question. We were getting data in our tests and they seemed sufficiently accurate. I'll investigate some more to understand why it was working. |
Browsers that use a page cache may not always fire onunload when a user navigates away from a page but doesn't close the window. They fire the pagehide event instead, and the pageshow event when the user returns to the page. It's better for us to use these events on browsers that support it. pageshow/pagehide also fire when onload/unload would normally have fired. Thanks to github user @solstice for the info in issue 43: YahooArchive#43 and the Surfin Safari blog: http://www.webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/
Browsers that use a page cache may not always fire onunload when a user navigates away from a page but doesn't close the window. They fire the pagehide event instead, and the pageshow event when the user returns to the page. It's better for us to use these events on browsers that support it. pageshow/pagehide also fire when onload/unload would normally have fired. Thanks to github user @solstice for the info in issue 43: YahooArchive#43 and the Surfin Safari blog: http://www.webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/
Change optimized trie to avoid string that trigger a XSS warning from NoScript
Unload code is not called on iPhone/iPad and there is no navigation timing API currently supported.
IPad/Iphone uses the “pagehide” event instead of “unload” event.
http://www.webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/
I tested this and it works. I'm new to git, but I'll try to send the code updates later today.
The text was updated successfully, but these errors were encountered: