- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Fri, 29 May 2015 07:55:16 +0000
- To: Paul Kinlan <paulkinlan@google.com>, "adrianba@microsoft.com" <adrianba@microsoft.com>
- CC: W3C Device APIs WG <public-device-apis@w3.org>, Travis Leithead <travis.leithead@microsoft.com>, Tobie Langel <tobie.langel@gmail.com>, "Bhaumik, Rijubrata" <rijubrata.bhaumik@intel.com>
Hi Paul, Adrian, Paul - I noticed you've been looking at the Ambient Light Events recently [0], and are considering whether it would be good to be shipped in Chrome stable without a flag. Other browser vendors have also publicly indicated they have either shipped it experimentally (Mozilla) or are working on it (Microsoft). TL;DR: the group has receiver implementation feedback from Mozilla, that the group is in process of fixing as we speak. Below is an update from ~couple of months ago I gave to the group. Since my update, the following has happened: Tobie (cc'd) has started to actively work on [5] and has indicated he should have the first draft out within days (Tobie - correct?). I'm wondering whether browser vendors would be more comfortable in: a) exposing the same feature through two different APIs: the current high level one reusing DOM Events [3] that has known issues, as well as the soon-to-be redesigned API that'll use [5] as the blueprint and gives web developers more control over the functionality, addresses the known issues, or b) just ship the redesigned API. Mozilla indicated [4] they'd like to see the issue fixed with an redesigned API, and that's what Tobie has been working on. Paul, Adrian - Please let us know your thoughts so that the group can plan accordingly. Thanks, -Anssi (Ambient Light spec editor) [0] https://code.google.com/p/chromium/issues/detail?id=336424#c20 > On 09 Apr 2015, at 15:01, Anssi Kostiainen <anssi.kostiainen@intel.com> wrote: > > 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 Friday, 29 May 2015 07:55:49 UTC