Bonus! I randomly discovered that Chrome's implementation of the "contentvisibilityautostatechange" event (boy, that's a mouthful) differs from Firefox's and WebKit's. Bug filed: issues.chromium.org/issues/365