- From: cowwoc <cowwoc@bbs.darktech.org>
- Date: Tue, 23 Jul 2013 23:50:01 -0400
- To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Hi Cullen, To be clear: The JS is asking the browser to tell it whether access to the camera was denied by the user, or by the browser for reasons outside the control of the user. The former is a recoverable error, the latter is fatal. Do you see any privacy implications there? Thanks, Gili On 23/07/2013 11:31 PM, Cullen Jennings (fluffy) wrote: > I think this will end up having privacy implications. For example, there was a bunch of discussion about the JS not being able to know if the user had selected a file or camera. > > Why would the JS need to know the difference between these two ? > > > On Jul 9, 2013, at 11:16 AM, cowwoc <cowwoc@bbs.darktech.org> wrote: > >> Hi, >> >> This is a follow-up discussion to https://code.google.com/p/chromium/issues/detail?id=257104 >> >> The WebRTC specification needs to provide a better error message in case the browser denies access to the camera, instead of the user. Currently, the specification states that >> PERMISSION_DENIED is >> the result of the user denying access. Instead of simply >> modifying the definition of >> PERMISSION_DENIED >> to cover both cases, I propose splitting it into separate cases: >> >> >> >> >> >> PERMISSION_DENIED_BY_USER >> >> >> >> PERMISSION_DENIED_BY_BROWSER >> >> >> >> >> >> >> >> Alternatively, >> we need to add a String error message alongside the enum, and >> require browsers to issue a different error message for each >> case. >> >> >> >> >> >> Thank >> you, >> >> Gili
Received on Wednesday, 24 July 2013 03:50:51 UTC