- From: Doug Turner <dougt@mozilla.com>
- Date: Wed, 9 May 2012 13:41:09 -0700
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: Anssi Kostiainen <anssi.kostiainen@nokia.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Hi Marcos,
> readonly attribute boolean near;
>
> or
>
> enum Proximity { "far", "near" };
> readonly attribute Proximity proximity;
Jonas asked me about this too. With high resolution proximity sensors defining what far and near mean is going to be difficult. I argued that if you have the min, max, value, and resolution you wouldn't need this.
> Lastly, there does not currently appear to be any normative text saying that the UA must only turn on the proximity sensor upon event registration (would suck if the sensor came on every time I open the browser, as it would just eat battery).
implementation detail. it doesn't need to be spec'ed out.
> Also, it might be good to have a bit of text describing what happens when you switch tabs in a browser (i.e., stop the sensor)… common sense stuff, I know… :)
UA policy. Happy with it as non-normative text, but lets not dictate this in the spec.
Regards,
Doug
Received on Wednesday, 9 May 2012 20:41:39 UTC