W3C home > Mailing lists > Public > public-device-apis-log@w3.org > November 2016

Re: [sensors] Should we request permission when sensor is not supported by the platform?

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Tue, 15 Nov 2016 20:33:44 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-260759229-1479242023-sysbot+gh@w3.org>
> @tobie 
> - 1 vs 3. Same error, different response times ;-)

No, that's incorrect. 3) has different error types for missing sensor 
(`NotReadableError`) and rejected permission request 

> If we agree that **Option 2 is the way to go**, we can explore 
further (although admittedly not much to go?). Probably no ideal 

Well, do we? This is a tradeoff between UX and fulfilling use cases on
 one side and increasing the browser's fingerprint by one bit per 
permission group on the other.

> Initial idea: 
> - as I said, we may instruct (non-normative suggestion) platforms to
 think in creative ways here about actual replies for permission calls
 to make it (functionally) act somewhat similar to Option 1 (think 
random delays). I realize it's not foreseen by Permissions API, it 
would only highlight new possible directions to pursue ;)

Can you be a bit more explicit here, and actually provide algorithm 
steps? I don't see how you'd make 2) look more like 1) without loosing
 the error distinction which is part we're interested in.

GitHub Notification of comment by tobie
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/145#issuecomment-260759229 using
 your GitHub account
Received on Tuesday, 15 November 2016 20:33:51 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:53 UTC