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 17:04:23 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-260701488-1479229461-sysbot+gh@w3.org>
There's a bunch of use cases, and thus improved UX, tied to developers
 having access to more detailed information about the underlying 
sensor.

For example: 

1. there's no point asking a user for the permission to access a 
sensor you know they do not have,
2. it's useful to try polling a sensor you've be given permission to 
but which has been disconnected,
3. it might be useful to explain to a user that they're forgoing some 
features by denying permission to access a sensor. It's impossible to 
do that if you can't distinguish between permission denied and missing
 hardware.
4. it's good to advise a user that they're sensor got disconnected or 
is suddenly no longer working, it's useless to tell them this if they 
actually revoked access.

>From a devX point of view, it's also better to send error events 
rather than to force the developer to set their own timeouts on the 
sensor and assume something is broken if they don't get data within x 
ms.

I'm sure we can do better than that.

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

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