This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Suggestion from Kiran Kumar: After calling getUserMedia(), the pop-up for user acceptance is waiting indefinitely for user acceptance. It would be better, if that prompt gets timed out after some time, and send a negative status response to the applications (the response may be permission_denied or user_time_out error). This proposal was initially made on the media-capture mailing list on August 29, 2013.
I'd like to propose a variation of this proposal. Instead of specifying a timeout, developers should be able to cancel a getUserMedia() call at any arbitrary time. If we implement a mechanism similar to setInterval(), clearInterval() then users will be able to cancel after a timeout (as Kiran suggested) as well as due to external (server-driven) events. This has UX benefits. Use-case: A user enters a video conferencing bridge. Before she grants permission to the camera, the call ends and all users are ejected from the room. Instead of asking users to respond to a stale prompt, the server can abort the operation and notify the user that the call has ended.
The time out I proposed here, will comprise of both the cases. 1. A default timer will be started after calling getUserMedia(). 2. A facility will be provided to the user to set his own timers (with some conditions for example very low or unacceptable values will be discarded). (In reply to Gili from comment #1) > I'd like to propose a variation of this proposal. > > Instead of specifying a timeout, developers should be able to cancel a > getUserMedia() call at any arbitrary time. > > If we implement a mechanism similar to setInterval(), clearInterval() then > users will be able to cancel after a timeout (as Kiran suggested) as well as > due to external (server-driven) events. This has UX benefits. > > Use-case: A user enters a video conferencing bridge. Before she grants > permission to the camera, the call ends and all users are ejected from the > room. > > Instead of asking users to respond to a stale prompt, the server can abort > the operation and notify the user that the call has ended.
Closing as "Won't fix". No consensus to change detected. A new bug may be opened in the future for considering whether it's possible to cancel a getUserMedia call, which would resolve this issue too, but that will not be in version 1.0.