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

Re: [proximity] The initial state of the proximity sensor (was: Tests and ref imp)

From: Marcos Caceres <w3c@marcosc.com>
Date: Wed, 23 May 2012 12:53:13 +0100
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <D3D606C8D2704923854D5060DEC8887C@marcosc.com>


On Wednesday, 23 May 2012 at 08:34, Anssi Kostiainen wrote:

> Hi,
>  
> On 23.5.2012, at 2.18, ext Marcos Caceres wrote:
>  
> > Having said that, not having the initial state of the proximity sensor is an issue (and should probably be marked as such in the spec).
>  
> By initial state, do you refer to the discussion we had around the alternative sync API proposal (navigator.proximitystate) that addressed this concern but was cumbersome to implement? Here's the old proposal:
>  
> http://dvcs.w3.org/hg/dap/raw-file/336825e8a8a2/proximity/Overview.html#the-proximitystate-attribute
Could not find the initial state in the link above, but I assume so…. I think your other email already addresses with with regards to determining freshness.  

--  
Marcos Caceres

http://datadriven.com.au  
Received on Wednesday, 23 May 2012 11:53:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 May 2012 11:53:47 GMT