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

Re: Next step for DAP Ambient Light Events

From: Doug Turner <doug.turner@gmail.com>
Date: Mon, 10 Sep 2012 14:49:13 -0700
Message-ID: <CAHni0v81m0rNBCRpaqZ1sToQ7mPwO2Ka78+RHj2Tjn8r2i3r_Q@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: François REMY <fremycompany_pub@yahoo.fr>, Marcos Caceres <w3c@marcosc.com>, Doug Turner <dougt@mozilla.com>, CSS WG <www-style@w3.org>, public-device-apis@w3.org
> For my own needs, yes.  The range names are more than sufficient for
> page/app styling based on light conditions.  You should only need to
> use the lux value if you're doing a game or something that wants a
> continuous value.

Exactly.  That is why we expose the lux value.  Removing the value
means reducing the use cases.

For what its worth, this conversation is similar to the discussion the
DAP had regarding proximity events.  Proximity sensors  report how far
an object is away from a sensor.  This is reported by the
DeviceProximityEvent.  However, we felt there was a need for a very
specific event that reported if the 'user' was near or far from the
sensor.  The use case is basically if the users's face is close to the
sensor or not.  For this, the UserProximityEvent was invented.

Maybe we should leave DeviceAmbientLight alone and add a new event
type for reporting changes in the general range of ambient lighting.

Received on Monday, 10 September 2012 21:49:39 UTC

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