- From: Steven Sokol via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Feb 2015 15:29:59 +0000
- To: public-media-capture-logs@w3.org
ssokol has just created a new issue for https://github.com/w3c/mediacapture-main: == Lack of timeout / cancellation leads to UI inconsistencies == (Long time listener, first time caller - please forgive any errors with regard to process or form.) The current standard does not appear to include a requirement that implementations provide a means of either: a) allowing application code to cancel a pending getUserMedia() request, thus removing the permissions UI element from the browser; or b) allow application code to set a timeout on the permission request for a getUserMedia() call, thus allowing the request to fail with a timeout error and the browser to withdraw the permission request element. This leads to an inconsistent state where the application code has given up but with the Navigator UI still displaying the permissions request dialog. This can lead to user confusion. I realize that to some degree this is a matter of implementation, but I think it would be worthwhile for the standard to include either a means of cancellation or a timeout. See https://github.com/w3c/mediacapture-main/issues/127
Received on Wednesday, 4 February 2015 15:30:15 UTC