Elad Alon

The problem originally stated in this issue appears to me unassailable. Curtailing the user's ability to capture arbitrary content would drive users away from the Web platform and towards native...

> I think if websites had the global screen recording state maybe via navigator.mediaDevices.isRecording > ... > Im not trying to prevent the user Regardless of our intentions, if we...

Are you thinking [DisplayMediaStreamConstraints.surfaceSwitching](https://github.com/w3c/mediacapture-screen-share/pull/225) here?

> Right, although the spec already allows to change the track source even without surfaceSwitching. Yes, surfaceSwitching is just a way for the application to hint to the user agent...

> @eladalon1983 Can we merge this PR now? I think it's better to wait for the experiment to reach 100%.

> > > @eladalon1983 Can we merge this PR now? > > > > > > I think it's better to wait for the experiment to reach 100%. > >...

> we might also want to limit switching between different displaySurface types, unless we have compelling use cases for that. Users want the flexibility to quickly change what they're sharing....

Not settling the promise means the following code would "hang", in that it never continues execution past `await`: ```js const devices = await navigator.mediaDevices.enumerateDevices(); doUsefulThings(devices); ``` No implementation I aware...

> but it comes with a non-negligible cost in terms of creating conflict when multiple PRs in parallel touch the same area of the spec If we format when no...

(We can massage and extend them to remove the focus on Chrome, either making them more generic, or covering various implementations, as applicable.)