- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Thu, 9 Apr 2015 12:01:31 +0000
- To: W3C Device APIs WG <public-device-apis@w3.org>
- CC: "adrianba@microsoft.com" <adrianba@microsoft.com>, Travis Leithead <travis.leithead@microsoft.com>, Tobie Langel <tobie.langel@gmail.com>, "Bhaumik, Rijubrata" <rijubrata.bhaumik@intel.com>
Hi All, Adrian, Travis, Tobie, I'm happy to see Project Spartan has started implement Ambient Light Events spec [1,2]. As the editor of the spec I'd like to make sure all the implementers have the same information re the spec status and its expected stability, so here's an update that should be of interest to Project Spartan: The Last Call 19 June 2014 spec [3] has two open issues which are expected to cause backwards incompatible changes: 1) Value not retrievable until a change causes the event to fire, raised by Mozilla [4]. 2) Apply the generic sensor API design pattern to the Ambient Light spec (also captured in [4]). To allow the spec to evolve, this feature is currently behind a flag in Chrome. Cc'ing Riju who implemented the feature in Chromium. I'm also cc'ing Tobie who's volunteered to push the generic sensor APIs effort [5] forward, that we expect to address both the open issues. I'd appreciate if the Microsoft participants (cc'd) could convey this spec status update to the Project Spartan team, and in turn provide Microsoft's implementation feedback to this group so that we could reshape the spec together. Thanks, -Anssi (Ambient Light spec editor) [1] https://twitter.com/IEDevChat/status/585928210828800000 [2] https://status.modern.ie/ambientlightevents [3] http://www.w3.org/TR/2014/WD-ambient-light-20140619/ [4] http://www.w3.org/2009/dap/track/issues/170 [5] https://github.com/w3c/sensors
Received on Thursday, 9 April 2015 12:02:06 UTC