- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Nov 2016 22:55:13 +0000
- To: public-device-apis-log@w3.org
> I recommend to request a permission prior to any attempt leading to accessing of a default sensor - and currently, "any sensor". Regardless of the sensor's existence. How would that work precisely, though? Would you really ask the user for permission? Or instead just return permission "denied"? What if the developer then tells the user that they can't get functionality x because they've "denied access to the gyroscope." Bad UX, especially if the user has no idea what a gyroscope is. This needs to be researched more thoroughly. We're trading privacy for bad UX and this is not a decision that can be taken lightly. It might even be worth considering leaving the option up to implementors. > Web developers currently have standard ways of checking whether a feature is available: https://w3c.github.io/sensors/#feature-detection I'm not sure where you're going with this. > I think that the current Generic Sensors API won't be shipping a sensor discovery API anyway? That's correct, but not sure either what you mean by this. > I'd say just write it down in the spec and let's see once it's down there. We need sound technical arguments here before we proceed. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/145#issuecomment-260490630 using your GitHub account
Received on Monday, 14 November 2016 22:55:20 UTC