> I can think of two ways that we can go ahead, implementing a device picker for mobile, or exposing all devices after gUM. The websites will still be able to detect we have different devices by looking at the device properties returned by the stream/track ... Today, websites cannot detect multiple devices if the user always chooses the same device in the Firefox (desktop) picker. The user would have to cycle through all their devices before this number matches the number of devices of their system. That said, if the user experience is going to be: - Internal Microphone 1 - Internal Microphone 2 - Internal Microphone 3 ...then users may end up having to cycle through them before finding the right one (not a great experience). In contrast, Firefox's device picker uses real labels. It also satisfies [§ 9.2. Use care when exposing APIs for selecting or enumerating devices](https://w3ctag.github.io/design-principles/#device-enumeration). I also think it mirrors how users unfamiliar with the Mediacapture API thinks it works — we get lots of bug reports from users who [think device selection happens in the browser](https://bugzilla.mozilla.org/show_bug.cgi?id=1142123#c13) today. That seems a better experience and tradeoff to me.
Bug 1899736 Comment 39 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> I can think of two ways that we can go ahead, implementing a device picker for mobile, or exposing all devices after gUM. The websites will still be able to detect we have different devices by looking at the device properties returned by the stream/track ... Today, websites cannot detect multiple devices if the user always chooses the same device in the Firefox (desktop) picker. The user would have to cycle through all their devices before this number matches the number of devices of their system. That said, if the user experience is going to be: - Internal Microphone 1 - Internal Microphone 2 - Internal Microphone 3 ...then users may end up having to cycle through them before finding the right one (not a great experience). In contrast, Firefox's device picker uses real labels. With RFP on, it also satisfies [§ 9.2. Use care when exposing APIs for selecting or enumerating devices](https://w3ctag.github.io/design-principles/#device-enumeration). I also think it mirrors how users unfamiliar with the Mediacapture API thinks it works — we get lots of bug reports from users who [think device selection happens in the browser](https://bugzilla.mozilla.org/show_bug.cgi?id=1142123#c13) today. That seems a better experience and tradeoff to me.
> I can think of two ways that we can go ahead, implementing a device picker for mobile, or exposing all devices after gUM. The websites will still be able to detect we have different devices by looking at the device properties returned by the stream/track ... Today, websites cannot detect multiple devices if the user always chooses the same device in the Firefox (desktop) picker. The user would have to cycle through all their devices before this number matches the number of devices of their system. That said, if the user experience is going to be: - Internal Microphone 1 - Internal Microphone 2 - Internal Microphone 3 ...then users may end up having to cycle through them before finding the right one (not a great experience). In contrast, Firefox's device picker uses real labels. With RFP on, it also satisfies [§ 9.2. Use care when exposing APIs for selecting or enumerating devices](https://w3ctag.github.io/design-principles/#device-enumeration). I also think it mirrors how users unfamiliar with the Mediacapture API think things works — we get lots of bug reports from users who [think device selection happens in the browser](https://bugzilla.mozilla.org/show_bug.cgi?id=1142123#c13) today. That seems a better experience and tradeoff to me.
> I can think of two ways that we can go ahead, implementing a device picker for mobile, or exposing all devices after gUM. The websites will still be able to detect we have different devices by looking at the device properties returned by the stream/track ... Today, websites cannot detect multiple devices if the user always chooses the same device in the Firefox (desktop) picker. The user would have to cycle through all their devices before this number matches the number of devices of their system. That said, if the user experience is going to be: - Internal Microphone 1 - Internal Microphone 2 - Internal Microphone 3 ...then users may end up having to cycle through them before finding the right one (not a great experience). In contrast, Firefox's device picker uses real labels. With RFP on, it also satisfies [§ 9.2. Use care when exposing APIs for selecting or enumerating devices](https://w3ctag.github.io/design-principles/#device-enumeration). I also think it mirrors how users unfamiliar with the Mediacapture API think things work — we get lots of bug reports from users who [think device selection happens in the browser](https://bugzilla.mozilla.org/show_bug.cgi?id=1142123#c13) today. That seems a better experience and tradeoff to me.