Elad Alon

> rejecting the getUserMedia request: this can be done today based on a timer/heuristic without changing the spec. (Reordered to put this most important part first.) What part of the...

> Step 6.3.7 states that: based on a previously-established user preference, for security reasons, or due to platform limitations, jump to the step labeled Permission Failure below. Thanks. You're right...

The application cannot currently cancel a call for gUM once it's in the pending state. That means that a call to gUM can result, several days later, in a user...

> > Suppose an application cares about when a Promise is zombified. > > Can you clarify why applications would actually care about this? Consider an application that records an...

It's interesting to note that Chrome has recently implemented the requirement for focus, and that this has led to bug reports from Web developers who were flummoxed by this new...

> I guess UAs can use a dedicated error message without any spec change. Is it best practice for Web apps to read the error message and break if it...

> What is the reason for the 1 second if I may ask ? Please note that 1s is the hard-limit, and normally the window of opportunity to calling `focus()`...

@jan-ivar and @youennf, I'd love to carry on from where we stopped at the end of the WebRTC WG Interim meeting yesterday. @youennf IIUC, your main concern was around the...

Btw, following the interim it became clearer to me which parts of my [proposed spec](https://eladalon1983.github.io/conditional-focus/index.html) were in need of clarification. I have made adjustments, mostly around (a) explaining the window...

> `...navigator.mediaDevices.displayMediaFocusMode = "no-focus";` I don't think this is going to "play nice" if the document is engaged in multiple concurrent captures. > it affects subsequent calls, but if you...