Re: [w3ctag/design-reviews] Sensor APIs (#207)

@annevk, any such user-facing strings are implementation details, but if you're interested in the Chrome's UX, see the [public UX document](https://docs.google.com/document/d/1XThujZ2VJm0z0Gon1zbFkYhYo6K8nMxJjxNJ3wk9KHo/). It should be noted that while the [Permissions registry](https://w3c.github.io/permissions/#permission-registry) specifies low level permission names for these sensors, implementations are encouraged to coalesce them into appropriate higher level concepts familiar to the user as needed. For example, it'd be rather bad UX to ask the user: "annevankesteren.nl wants to access your gyroscope [Block] [Allow]"

If your question is more broadly about the security and privacy protections in place, it is better answered by the [security and privacy assessment](https://github.com/w3c/sensors/blob/master/security-questionnaire.md) linked to from the initial TAG review request and the quite extensive [security and privacy](https://w3c.github.io/sensors/#security-and-privacy) section of the Generic Sensor API spec and the equivalent sections in the derived specs for sensor-specific considerations, risks, and mitigation strategies.

Thanks for reviewing this work. We'd warmly welcome further feedback from Mozilla to make sure you'd feel good about implementing these APIs in the future.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/207#issuecomment-350049348