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

RE: Next step for DAP Ambient Light Events

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Tue, 18 Sep 2012 23:53:57 +0000
To: Doug Turner <doug.turner@gmail.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>, Tab Atkins Jr. <jackalmage@gmail.com>
Message-ID: <84BCA539DD96614691177EDA3CE4FF0546BDB168@ORSMSX101.amr.corp.intel.com>
>> I think it makes more sense to only fire when you go from one state to another such as from bright -> normal
>>
> That is correct.  Was there something in the draft that needed to be clarified?

In section 6.2.2 in the NOTE paragraph is not clear. The sentence above that as "When the current light changes, the user agent must fire a light level event." Is not clear either. When the light changes for instance from 300 lux to 305 lux, but it is within the "normal" range, so I assume you don't want to fire the LightLevelEvent.

Thanks
/dt/


-----Original Message-----
From: Doug Turner [mailto:doug.turner@gmail.com] 
Sent: Tuesday, September 18, 2012 4:30 PM
To: Tran, Dzung D
Cc: public-device-apis@w3.org; Tab Atkins Jr.
Subject: Re: Next step for DAP Ambient Light Events

> I don't see any mention of the range for normal. Was this done on purpose?

I thought it was obvious that this range is between bright and dim.
Maybe we should call that out?

> I think it makes more sense to only fire when you go from one state to another such as from bright -> normal

That is correct.  Was there something in the draft that needed to be clarified?
Received on Tuesday, 18 September 2012 23:54:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 18 September 2012 23:54:26 GMT