Transition Level 2 to CR

[igrigorik]

• [x] Known / outstanding spec issues
  • [x] document updates from L1
  • [x] update ack's section for L2
• [x] Web platform tests
  • https://github.com/w3c/web-platform-tests/tree/master/page-visibility
• [x] Privacy and security
  • https://github.com/w3c/page-visibility/pull/27
• [ ] Implementations
  • Chrome: M56+
  • Firefox: M18+
  • Edge: TODO.
  • Safari: WIP, https://bugs.webkit.org/show_bug.cgi?id=151234
• [x] Public signals: adoption, feedback...
  • https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API
  • https://www.igvita.com/2015/11/20/dont-lose-user-and-app-state-use-page-visibility/

[igrigorik]

@toddreifsteck @plehegar please review above updates.

I believe the spec itself is good to publish. I reviewed the tests and I believe we have all the bits covered there. The only small gotcha is that only FF currently passes the unload test case; I'm hoping we'll land the fix soon in Chrome -- currently behind a flag. That said, I don't think this should block us from proceeding with the transition.

[plehegar]

👍

[igrigorik]

Approved CR transition: https://www.w3.org/2016/10/26-webperf-minutes.html

[plehegar]

I republished the document for wide review. Should request the move in 2 weeks since I don't really expect folks to comment on this update.

[toddreifsteck]

Microsoft Edge Bug is https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/5405698/

[plehegar]

I haven't seen additional comments on this front, so I'll request CR status.

[plehegar]

scheduled for publication tomorrow

[plehegar]

Published at https://www.w3.org/TR/2016/CR-page-visibility-2-20161122/ Next step would be PR in January.

[igrigorik]

\o/ ... updated status on our spreadsheet, closing this.

Thanks everyone!

[toddreifsteck]

Edge has fixed this in private branches. It is "coming soon" to an Insider build!