W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2020

Re: [mediacapture-main] Add semantics choice to getUserMedia() for in-browser picker. (#667)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 Mar 2020 15:02:12 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-601229126-1584630130-sysbot+gh@w3.org>
> * Presumably, the transition plan is for GetUserMediaSemantics to default to user-chooses initially, then eventually to not permit browser-chooses

As I recall, we did not reach consensus on a transition plan last virtual interim, just [option B](https://docs.google.com/presentation/d/1NIHzumglY9cYa4b7rcEbHGVsMam5BiY80VfFDB6cDjQ/edit?ts=5e2b3630#slide=id.g7ead6f3266_5_70) for now.

So there are no transition impacts from this PR, since it effectively defaults to `"browser-chooses"` for backwards compatibility (yet allows Firefox to prompt like it does today).

This is the minimal consensus needed to replace labels and in-content selection.

> How does the application determine what choices are available?

Like it does today, count devices per kind using *enumerateDevices*. Although if constraints are used, this might narrow choices, and it could be hard to detect. Right now I think the API would succeed right away without a prompt in that case (assuming you already have access to the current device). Would you like it to fail? That would be a bigger semantic difference.

The feature detection is there to let us start using this before labels go away.

> Reading the PR, I wasn't sure whether "user-chooses" always results in a prompt.

It does not. Only when there's a choice. Otherwise, only a permission prompt is mandated.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/pull/667#issuecomment-601229126 using your GitHub account
Received on Thursday, 19 March 2020 15:02:14 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:50 UTC