We have three categories of solutions suggested here: - Throttling - An explicit gesture to approve using the API - A prompt
We might be able to do some/all of those depending on the situation. Is there anything else I have missed that has been suggested? I honestly would like to request we do some user studies on different content strings for prompts and see if users understand the risks. Prompts are a UX pattern that are convention already, inventing new ones will take more experimenting to perfect. So if we can find the right content where users understand some of the time, this is better than not giving users the ability to ever understand where their data is going. Thanks On Thu, Jan 11, 2018 at 7:20 AM, Anne van Kesteren <ann...@annevk.nl> wrote: > On Thu, Jan 11, 2018 at 5:39 AM, Chris Van Wiemeersch <c...@mozilla.com> > wrote: > > Anne and Martin, can you think of changes to request for the Sensor API > > that we would resolve or reasonably improve the existing fingerprinting > > concerns? > > It sounds like Chrome's approach is throttling, which would probably > work, but it doesn't work for WebVR, right? (At which point we're back > at looking at a permission prompt and being unsure how to phrase the > question.) > > > -- > https://annevankesteren.nl/ > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
