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

Re: [ambient-light] Security and Privacy considerations for ALS

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Jun 2017 11:37:06 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-309726654-1497958625-sysbot+gh@w3.org>
> My understanding is, the light-level media query as specified cannot be implemented in an interoperable manner, and as such, is not a solution to pursue at this time.

Source? The CSS WG [does not seem to have an open issue about this](https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue+is%3Aopen+label%3Amediaqueries-5), despite having included light-level in [Mediaqueries Level 5](https://drafts.csswg.org/mediaqueries-5/#light-level) which it published very recently.

As an aside, the note in the light-level section (copied below) is well worth a read (and might help either find alignment if some of the use cases match or, on the contrary, clarify that they're orthogonal concerns):

>Even though it is expected that User Agents will adjust the value of this media feature based on ambient light sensors, this specification intentionally refrains from defining the three levels in terms of a measurement in lux, for several reasons:
>* Devices equipped with a light sensor usually adjust the brightness of the screen automatically. Depending on the level of adjustment, the thresholds for needing a low contrast or hight contrast content may vary.
>* Different screen technologies wash out at very different ambient light levels; e-ink displays remain readable in bright daylight, while liquid crystal displays do not.
>* Many embedded light sensors are inaccurately calibrated, making it difficult to establish useful thresholds valid across devices.

GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/ambient-light/issues/13#issuecomment-309726654 using your GitHub account
Received on Tuesday, 20 June 2017 11:37:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC