- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Nov 2019 14:39:40 +0000
- To: public-webrtc-logs@w3.org
I see some value in 'enabled' as it stands but also see value in making it evolve. There is a trick in trying to make it closer to muted though. A web page can set enabled to false and set it back to true whenever it wants. For instance when the page is in the background, which might be hard to notice especially in case of microphone. On the contrary, if a web page stops capture, the web page will not be able to restart capture in the background. If the web page stops capture for a long time, Safari will also for instance trigger a reprompt. Prompting behaviour can be adjusted naturally with async getUserMedia, this is not as easy with 'enabled'. We could try to emulate enabled=true as a sort of calling getUserMedia again with a mixture of enabled/muted/ended/user gesture restriction/focus mitigation. Not sure whether that is worth it. I also find the argument of the excessive reprompting a bit odd. There is nothing preventing Firefox to not prompt for a getUserMedia call in that kind of situation where enabled would be used with the same effect. Firefox could for instance render the 'gray' icon instead of reprompting. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/642#issuecomment-556031585 using your GitHub account
Received on Wednesday, 20 November 2019 14:39:42 UTC