Add a performance entry type for visibility state changes

[noamr]

The entry is added when the visiblity changes for any reason, and an initial entry is added when the document becomes active.

See https://github.com/w3c/performance-timeline/issues/105 See also https://github.com/w3c/page-visibility/issues/29

This is the solution that was proposed at WebPerfWG (TODO add link to minutes) See Design review at CTAG

• [ ] At least two implementers are interested (and none opposed):

  • Already implemented in Chrome behind experimental flag
  • WebKit: ?
  • Mozilla: ?

• [x] Tests are written and can be reviewed and commented upon at:

  • https://github.com/web-platform-tests/wpt/pull/35620

• [ ] Implementation bugs are filed:

  • Chrome: 1103451
  • Firefox: …
  • Safari: …
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …

(See WHATWG Working Mode: Changes for more details.)

---

/browsers.html ( diff ) /index.html ( diff ) /infrastructure.html ( diff ) /interaction.html ( diff ) /references.html ( diff )

[noamr]

LGTM. Needs the PR template filled out, and then we can merge.

Thanks! I'm still working on the WPTs :)

Somewhat favorable Mozilla position

I don't see any Mozillan positions in that thread?

You're right, I saw @dbaron's name (it's from the time when he was still at Mozilla) but it's W3CTag. @dbaron do you remember who from Mozilla was involved in this? /cc @emilio

[emilio]

@sefeng211 does the performance team have any concern with this?

[domenic]

Ping @sefeng211 for any opinions from Mozilla?

[sefeng211]

This looks good from our side.

[domenic]

Thanks! @noamr I'll wait to merge this until you give the sign that you're ready to ship this in Chromium, and file appropriate Gecko/WebKit bugs. Also if you could fix the merge conflicts that would be lovely.

[noamr]

Thanks! @noamr I'll wait to merge this until you give the sign that you're ready to ship this in Chromium, and file appropriate Gecko/WebKit bugs. Also if you could fix the merge conflicts that would be lovely.

On it. AFAICT the chromium implementation has been ready for a while, will double check and start the I2S thing etc. thanks!