W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2014

Re: Ambient light API redesign

From: Tobie Langel <tobie.langel@gmail.com>
Date: Fri, 29 Aug 2014 13:05:43 +0200
Message-ID: <CAMK=o4f5mn7Wgw+iD78YjkDLewhYvWDm2Ji0ORnSE4SEvnE8rg@mail.gmail.com>
To: Marcos Caceres <marcos@marcosc.com>
Cc: Jonas Sicking <jonas@sicking.cc>, "public-device-apis@w3.org" <public-device-apis@w3.org>, Anssi Kostiainen <anssi.kostiainen@intel.com>, public-script-coord <public-script-coord@w3.org>, Doug Turner <dougt@mozilla.com>, Rick Waldron <waldron.rick@gmail.com>, Domenic Denicola <domenic@domenicdenicola.com>, Anne van Kesteren <annevk@annevk.nl>
On Tue, Aug 26, 2014 at 11:17 PM, Marcos Caceres <marcos@marcosc.com> wrote:

> We are actually discussing this on Twitter right now. It seems you don't
> need the promise. The constructor causes the subscription to the sensor,
> and then you can potentially just observe `.value` until it gets updated.

How do you handle permissioning with that model?

More precisely, how do you handle cases when access is refused?

Should there be an onerror callback?

Secondly, must the onchange event be called when .value is changed from
null to its first value? Seems to be useful in a number of scenarios (e.g.
do something with the first value and do it again whenever there's a value

Received on Friday, 29 August 2014 11:06:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:11 UTC