- From: jnoring via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Jan 2016 17:51:17 +0000
- To: public-media-capture-logs@w3.org
jnoring has just created a new issue for https://github.com/w3c/mediacapture-main: == gUM firing repeatedly for the same page load == I wanted to start a discussion around this defect: https://bugzilla.mozilla.org/show_bug.cgi?id=1212996 The bug basically boils down to this: in Firefox, every call to getUserMedia will show the gUM allow/deny prompt. Example: 1. I visit https://www.xyz.com, which requests access to camera/microphone 2. gUM fires, showing the browser's allow/deny dialog 3. User allows 4. xyz.com has support for navigator.mediaDevices.enumerateDevices() and allows the user to change mic and camera in page 5. User changes their mic or camera 6. gUM fires, again showing the browser's allow/deny dialog ...step 6 is really the question: should a browser show that second allow/deny dialog? Currently Chrome and Firefox are completely different in this regard: 1. Chrome: if the page is loaded via HTTPS, not only does that first allow grant the page access to *all* microphones and cameras, but it does so in perpetuity; the action is interpreted as permanent for that page. 2. Firefox: unless the user explicitly chooses the "allow always" option in the gUM dialog, Firefox prompts for every single gUM request, even if the user has already granted access. Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/304 using your GitHub account
Received on Monday, 11 January 2016 17:51:20 UTC