Re: [mediacapture-main] gUM firing repeatedly for the same page load

It doesn't address the basic problem.

The problem is: page creates custom UI for enumeration/selection of 
devices.  User changes devices.  gUM prompt fires a second time (which
 offers the user to change their choices--somewhat).  This has several
 serious consequences, as I mentioned previously:

1. A user could reject the second request (most likely accidentally), 
which means every time user swaps mic/camera, the page has to be ready
 to get rejected for permissions reasons.  If they are already 
chatting with someone, and they are rejected, then that video 
conference is over.  If they accidentally reject only mic, or only 
camera, then the page has to account for that and the user experience 
is bizarre.
2. During an actual call, showing the gUM prompt means a user could be
 absent for seconds or more while they answer the dialog.
3. Confusing user experience; the dialog shows in response to camera 
or mic selection in-page, and suddenly they're being given a further 
permissions dialog.  Some of this can be mitigated by specifying an 
"exact" device in gUM, but it is still bizarre from a user standpoint.

I don't see how a preview addresses these issues.  It's a cool 
feature, sure, but it doesn't solve the basic problem between device 
enumeration/selection and permissions that the spec is rather quiet 
about.

-- 
GitHub Notification of comment by jnoring
Please view or discuss this issue at 
https://github.com/w3c/mediacapture-main/issues/304#issuecomment-174064364
 using your GitHub account

Received on Friday, 22 January 2016 21:52:31 UTC