W3C home > Mailing lists > Public > public-device-apis-log@w3.org > September 2017

Re: [sensors] What's the rationale of moving security checks outside of normative requirements?

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Tue, 26 Sep 2017 08:53:38 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-332131947-1506416006-sysbot+gh@w3.org>
Each condition of the security check used to be a RFC 2119 "MUST" requirement, they're now used as examples for something the user agent "can" do (whatever that means is up to interpretation, and it's arguably non-normative):

> The user agent can define the list of conditions to check if it can expose sensor readings.
> The example list of conditions is presented below:

So there's a massive difference between the current state of things and what it used to be. I'm kind of surprised this actually needs to be stated.

GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/287#issuecomment-332131947 using your GitHub account
Received on Tuesday, 26 September 2017 08:53:32 UTC

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