Re: [sensors] Ambient Light and the generic sensor API design

I think Tim also had a proposal for a generic Sensor API design.

Would you be interested to discuss this during TPAC? I would gladly
create a breakout session for this.

-- Mounir

On Fri, 3 Oct 2014, at 18:13, Kostiainen, Anssi wrote:
> Hi All,
> 
> We’ve now experimentally implemented the LCWD version of the Ambient
> Light Events spec [1] in Chromium. It is in Chrome Canary channel behind
> the chrome://flags/#enable-experimental-web-platform-features flag.
> 
> We plan to keep the feature behind the flag until we've reshaped the API
> surface in this group to address the two issues raised (both capture in
> ISSUE-170):
> 
> 1) Value not retrievable until a change causes the event to fire, raised
> by Mozilla [2].
> 
> We’ve worked around this in the experimental Chromium implementation by
> firing the event when an event listener is added. However, relying on
> such a side-effect has known issues, and we understand the hesitation of
> other implementers to proliferate this pattern.
> 
> 2) Establish a common pattern for sensor APIs and apply the design to the
> Ambient Light spec.
> 
> Rick Waldron who recently joined the group has been experimenting with a
> generic sensor API design [3]. The proposed design would fix the above
> issue 1) too.
> 
> To make it easier for interested parties to collaborate on the redesign,
> I've migrated the Ambient Light Events Editor’s Draft [4] to GitHub [5]
> (from Hg).
> 
> All - your thoughts? Volunteers to help drive this forward?
> 
> Thanks,
> 
> -Anssi
> 
> [1] http://www.w3.org/TR/2014/WD-ambient-light-20140619/
> [2]
> http://lists.w3.org/Archives/Public/public-device-apis/2014Aug/0058.html
> [3] https://github.com/rwaldron/sensors
> [4] http://w3c.github.io/ambient-light/
> [5] https://github.com/w3c/ambient-light/

Received on Friday, 3 October 2014 10:01:25 UTC