Wotcher TAG!

I'm requesting a TAG review of site-initiated mirroring.

We're proposing an API to allow Web pages to request mirroring themselves to a secondary display. They will be allowed to request customization of the mirroring implementation in certain respects.

• Explainer¹ (minimally containing user needs and example code): https://github.com/webscreens/site-initiated-mirroring/blob/main/explainer.md
• User research: N/A
• Security and Privacy self-review²: https://github.com/webscreens/site-initiated-mirroring/pull/3
• GitHub repo (if you prefer feedback filed there): https://github.com/webscreens/site-initiated-mirroring
• Primary contacts (and their relationship to the specification):
  • Takumi Fujimoto (@takumif), Google (spec proposer)
  • Mark Foltz (@mfoltzgoogle), Google (spec proposer, Presentation API spec editor)
  • Anssi Kostiainen (@anssiko), Intel (Second Screen WG chair)
  • Louay Bassbouss (@louaybassbouss), Fraunhofer Gesellschaft (Second Screen WG chair)
• Organization/project driving the design: Google Chrome
• External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5648093276012544

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• The group where the incubation/design work on this is being done (or is intended to be done in the future): Second Screen WG/CG
• The group where standardization of this work is intended to be done ("unknown" if not known): Second Screen WG
• Existing major pieces of multi-stakeholder review or discussion of this design: https://www.w3.org/2021/10/26-webscreens-minutes.html#t03
• Major unresolved issues with or opposition to this design: N/A
• This work is being funded by: The explainer was written by and the Chromium implementation is being worked on by Google employees.

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

🐛 open issues in our GitHub repo for each point of feedback