[w3ctag/design-reviews] Capture Handle (#645)

Ya ya yawm TAG!

I'm requesting a TAG review of `Capture Handle`.

The proposed capture handle is a mechanism that allows a web-application to ergonomically and confidently identify the web-application which it is display-capturing - provided that the captured application has opted-in. Such identification allows these two applications to collaborate in interesting ways. For example, if a VC application is capturing a presentation, then the VC application can expose user-controls for previous/next-slide directly in the VC application. This lets the user navigate presentations without having to jump between the VC and presentation tabs.


  - Explainer: https://docs.google.com/document/d/1oSDmBPYVlxFJxb7ZB_rV6yaAaYIBFDphbkx5bXLnzFg/edit?usp=sharing

  - Specification URL: https://eladalon1983.github.io/capture-handle/

  - Tests: N/A
  - Security and Privacy self-review: https://github.com/eladalon1983/capture-handle/blob/main/security-privacy-questionnaire.md

  - Primary contacts (and their relationship to the specification):
      - Elad Alon (@eladalon1983), Google
  - Organization(s)/project(s) driving the specification: Google
  - Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/w3c/mediacapture-screen-share/issues/166

  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/4854125411958784


Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://w3ctag.github.io/design-principles/)
  - Relevant time constraints or deadlines: Origin Trial has started in Chrome m92
  - The group where the work on this specification is currently being done: WebRTC WG
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): WICG ([thread](https://discourse.wicg.io/t/proposal-capture-handle-bootstrap-app-collaboration-when-screensharing/5354/))
  - Major unresolved issues with or opposition to this specification: Mozilla worries this makes getDisplayMedia too attractive and would make it hard to nudge the Web over to using getViewportMedia - a long-term vision of theirs which Chrome does not currently share. Apple engaged cooperatively at first, but after their proposals were adopted, they mused about possible changes of direction, then disengaged; their public position is not clear at the moment.
  - 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 @eladalon1983


-- 
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/645