According to http://caniuse.com/#feat=pagevisibility Chrome, Opera, and Blackberry browsers use the webkit prefix for the event "visbilitychange" that gets fired on the document

jQuery does not seem to handle this case when binding to the "visbilitychange" event. The workaround is to bind to both the visibilitychange and webkitvisibilitychange event. However, if/when Chrome decides to fire the correct event name, this may cause the event handler to fire twice, as it does in firefox when listening for both visibilitychange and mozvisibilitychange, which was the old interface for FF10 according to https://developer.mozilla.org/en-US/docs/Web/Reference/Events/visibilitychange

Example of the problem (Chrome): http://jsfiddle.net/tomprogramming/YCrJA/1/

Example of the workaround (Chrome):

http://jsfiddle.net/tomprogramming/YCrJA/2/

Example of firefox firing twice (MUST use firefox to view):

http://jsfiddle.net/tomprogramming/YCrJA/3/

It would be nice to just put in

jQuery(document).on("visibilitychange", handler);

and have it work in a manner similar to the mouseenter/mouseleave=>mouseover/mouseout handling.