[w3ctag/design-reviews] VisibilityStateEntry (#534)

Saluton TAG!

I'm requesting a TAG review of VisibilityStateEntry.

Exposes the initial visibility state of the page plus any visibility state changes that the page goes through to the PerformanceObserver, with buffered flag support.


  - Explainer (minimally containing user needs and example code): [url](https://docs.google.com/document/d/1l5kHiJRkdQwEN-CYI5_mUNODhQVB5rCyjN4jHDdXDHA/edit#)
  - Security and Privacy self-review: I did not fill it out because the API does not really expose information that is not already available via the PageVisibility API. But if desired I can fill it out.
  - GitHub repo (if you prefer feedback filed there): I will be adding this feature on this [repo](https://github.com/w3c/page-visibility) but feel free to comment on the doc or this issue for now.
  - Primary contacts (and their relationship to the specification):
      - [Nicolás Peña Moreno](@npm1), Google, will do the spec work.
      - [Ilya Grigorik](@igrigorik), Google, WebPerf chair.
      - [Nic Jansma](@nicjansma), Akamai, WebPerf chair.
      - [Yoav Weiss](@yoavweiss), Google, WebPerf chair. 
  - Organization/project driving the design: Chromium
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status):

Further details:

  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - The group where the incubation/design work on this is being done (or is intended to be done in the future): W3C WebPerf WG
  - The group where standardization of this work is intended to be done ("unknown" if not known): W3C WebPerf WG
  - Existing major pieces of multi-stakeholder review or discussion of this design: see call [minutes](https://docs.google.com/document/d/1PMbJ8kUHtrrCZxHJfKXcV0YQeTxyMOH4AORgd2VuhOw/edit)
  - Major unresolved issues with or opposition to this design: N/A
  - This work is being funded by: Google

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify @npm1


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/534