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

Re: [mediacapture-main] "user-chooses": Does required constraints make any sense now? (#669)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Mar 2020 20:16:56 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-603482320-1585081015-sysbot+gh@w3.org>
@youennf Let's not confuse API with user experience. Firefox has had a picker forever. Join us. 😉

@henbos I'd caution against oversimplifying the problem. While it may seem appealing to expose prompt methods wholesale to JS, they're often a bad idea (see permission.request() or roc's [old blog](https://robert.ocallahan.org/2011/06/permissions-for-web-applications_30.html)).

There's a role for user agents to negotiate permission at an app's _point of (media) access_.

Thus the _media access API_ design is still an abstraction separate from a user agent's prompting story, even when that API puts requirements on it.

I don't even agree _"consistent prompting behavior across browsers"_ is a general goal. That's a common _web developer_ ask, a different problem from what we're solving (end user privacy).

For instance, Firefox has not committed to removing its prompt on seeing `"browser-chooses"`, and there's no spec language to force it, because that wasn't the goal.

The goal of `"user-chooses"` was to minimally guarantee a prompt only when the user's choices exceed what the app asks for, allowing apps to replace their "control setting"-type pickers with it.

Like today, the app remains in control of what it wants to ask.

> if the prompt is actually good enough to do its job, why would prompting be a problem?

Because users don't want to be prompted for their camera and microphone every time.

@henbos I don't want to dismiss criticisms that constraints were over-designed (they were), and while I'm glad `"user-chooses"` sparked an _opportunity_ to think further, the two events seem largely orthogonal.

That's important to stress since @youennf seems to suggest UX has to come before API here, even though the workin group agreed last interim to move ahead with https://github.com/w3c/mediacapture-main/pull/667.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/669#issuecomment-603482320 using your GitHub account
Received on Tuesday, 24 March 2020 20:16:59 UTC

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