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: youennf via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Mar 2020 11:06:30 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-603175247-1585047989-sysbot+gh@w3.org>
If we go with a device picker, we should design it for the best user experience, from scratch.
If we have to update the API to make sure the user experience is great, we should probably do it.
Once we have a good model, we should think of the transition plan.

> Last point: I don't think a transition plan to a more limited API will succeed.

It depends. You could always reduce the power of the old API, for instance by only selecting the default devices with the old API (after some deprecation time) and using constraints as ideal in that case.

Also, I doubt that the fact of modifying how we handle constraints will be seen as a more limited API. I might be biased but to me, constraints are over-complex and sub-used. Simplifying constraints would be beneficial.

GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/669#issuecomment-603175247 using your GitHub account
Received on Tuesday, 24 March 2020 11:06:31 UTC

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