- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2023 10:35:43 +0000
- To: public-webrtc-logs@w3.org
> What benefit would this distinction have? I don't think it exists in Firefox and Chrome. Does it exist in Safari?
It used to be like this in Safari. It could happen in the future.
> Uses of multiple cameras seem different from multiple uses of the _same_ camera. I don't see the connection.
Say you do the following:
```
const track1 = navigator.mediaDevices.getUserMedia({video: {facingMode: 'environment', width:640});
const track2 = navigator.mediaDevices.getUserMedia({video: {facingMode: 'environment', width:1280});
```
Everything works fine. Now you start another capture:
```
const track3 = navigator.mediaDevices.getUserMedia({video: {facingMode: 'user', width:640});
```
In that case, you might still be able to capture the environment at 640 but not at 1280.
If track1 and track2 share the same source, WebKit would probably fail both of them, but only track2 would be ended if they would not share the same source.
I guess the alternative would be to fire a configurationchange event on track2.
> The _minimum_ granularity has to be at least the JS [realm](https://html.spec.whatwg.org/multipage/webappapis.html#concept-realm-global) for the spec to work, i.e. the `mediaDevices` object.
Right, I guess we could change this if there was a use case for it but it does not seem worth it.
If the source granularity was the top page, [[devicesLiveMap]] would also start to be out of sync as well.
Can we settle on source granularity being the JS realm then?
If so, it might be worth clarifying this in the spec.
--
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/940#issuecomment-1475984559 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 March 2023 10:35:45 UTC