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

Re: [sensors] Device Proximity (was: Device light and proximity sensor)

From: Doug Turner <dougt@mozilla.com>
Date: Wed, 9 May 2012 14:21:20 -0700
Cc: Marcos Caceres <w3c@marcosc.com>, Anssi Kostiainen <anssi.kostiainen@nokia.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <51A6BF97-08D8-4D34-A34E-8B3CD9CBA0DE@mozilla.com>
To: "Tran, Dzung D" <dzung.d.tran@intel.com>

On May 9, 2012, at 2:13 PM, Tran, Dzung D wrote:

>> So, what I agreed with jonas about was a new event that only fired when there was a transition between near and far.  device proximity for something that was more advanced.  <insert this new event name here> for something really simple. 
>> Thoughts?
> What I am afraid of is that browsers going to interpret far versus near differently on the same device. I rather to give the control to the programmer to interpret base on value, min, max.

Exactly.  That is why I resist the new event -- and having things like 'near' and 'far'.  I'd rather report exactly what I know over hiding the things I know behind named strings.

Received on Wednesday, 9 May 2012 21:21:50 UTC

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