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

> Can I ask that you bring the explainer into the WICG repo at a stable URL?

It's now in the root of the WICG repo.

> Also, can you let us know more of the background of why this is being done in WICG as opposed to the webrtc wg?

**Mozilla** has been opposing this and cited two arguments:
1. That they are concerned that this will make getDisplayMedia "too attractive" and delay adoption of getViewportMedia. Note that:
    1. Deprecating getDisplayMedia is not under discussion (and Chrome would oppose). So making getDisplayMedia "too attractive" is not relevant criticism of Capture Handle.
    2. getViewportMedia has been under meandering discussion for close to a year now, and it's unclear when/if it will eventually be specified, let alone implemented.
2. Mozilla has brought in their own proposal to address some of the use-cases handled by Capture Handle, but not all, using "Slide Controls." I applaud their efforts and will be cheering them on, but since Capture Handle addresses additional use-cases, I do not see that as relevant opposition either.

**Apple**'s position has been unclear. They have made proposals for changes to Capture Handle. When those proposals were adopted, Apple suggested reconsidering the entire approach. A definitive answer of what approach would satisfy Apple has not yet been given.

> What's the trajectory for this after incubation in WICG?

I believe it's time to put this in web-developers' hands, show them how useful it is for them, and use their positive feedback to motivate progress in the WebRTC WG.


-- 
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#issuecomment-878959308