On Tue, Jun 30, 2015 at 3:02 PM, Nick Doty <npdoty@w3.org> wrote: > On Jun 30, 2015, at 5:54 PM, Eric Rescorla <ekr@rtfm.com> wrote: > > > On Tue, Jun 30, 2015 at 2:49 PM, Nick Doty <npdoty@w3.org> wrote: > > >> I would prefer it if we could design APIs as much as possible so that >> browsers don't need to make a choice between functionality and exposing >> additional information about a user. Yes, users should be able to just turn >> off functionality together and sometimes will feel the need to do so, but >> if we can design a feature so that a large number of use cases don't >> require such a trade-off, then we can benefit from that. >> > > Sure, but I don't think shoving more permissions dialogs at the user is > the right way to do it. > Martin Thomson has suggested using double keying here. Would people > consider that > satisfactory? > > > Have to get on a plane, so can't reply to all your comments in this thread > in detail right now, but I just wanted to say that I absolutely agree that > adding more permission prompts isn't necessarily the answer, and likely > isn't. > > Can you or Martin detail what the double-keyed proposal would be? > Just having the identifiers be scoped both to the origin and the containing origin. > The number of permission prompts wouldn't need to change if some of the > values exposed are just exposed *after* granting permission to access the > camera or microphone. > Yes, we discussed that, but there's not really any logical connection between these two. -Ekr
Received on Tuesday, 30 June 2015 22:13:43 UTC