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

Re: Next step for DAP Ambient Light Events

From: François REMY <fremycompany_pub@yahoo.fr>
Date: Mon, 10 Sep 2012 22:43:56 +0200
Message-ID: <3000F4F398E14A4382772611F8C9263E@FREMYD2>
To: "Tab Atkins Jr." <jackalmage@gmail.com>, "Doug Turner" <doug.turner@gmail.com>
Cc: "Marcos Caceres" <w3c@marcosc.com>, "Doug Turner" <dougt@mozilla.com>, "CSS WG" <www-style@w3.org>, <public-device-apis@w3.org>
> It looks like they have to be, yes.  For clarity I'd probably define,
> in a clearly-marked informative section, what lux values the ranges
> map to in an ideal sensor, but have a strong note that UAs should
> (RFC2119 SHOULD) adjust the ranges to respect the device's own
> sensitivity, so as to achieve the same results.

The whole point is that the 'dim' and 'bright' modes depends of the screen's 
minimal/maximal brightness and reflectance, too.

While an approximative settings is important, ultimately, switching to a 
high-contrast layout (either black on white or white on black) may depends 
on more than just the value in lux returned by the ALS. As such, I agree 
with Tab that the specification should advertise the fact that the range in 
which a particular mode is triggered is completely to the discretion of the 
user agent, which will do so in order to provide the best experience 
possible to the user. 
Received on Monday, 10 September 2012 20:44:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:55 UTC