W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2012

Re: [sensors] Proximity Events

From: N.V.Balaji <nv.balaji@samsung.com>
Date: Tue, 22 May 2012 19:01:41 +0530
Message-id: <C842B897E03041F9B9F6DC1279FD9973@sisodomain.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>, Robin Berjon <robin@berjon.com>
Cc: Doug Turner <dougt@mozilla.com>, public-device-apis@w3.org

-------------------------------------------------
From: "Bjoern Hoehrmann" <derhoermi@gmx.net>
Sent: Monday, May 21, 2012 8:39 PM
To: "Robin Berjon" <robin@berjon.com>
Cc: "Doug Turner" <dougt@mozilla.com>; <public-device-apis@w3.org>
Subject: Re: [sensors] Proximity Events

> It's the same problem and suffers from the same conceptual flaw (if you
> add a second listener there is no reason to trigger the first listener).
> http://lists.w3.org/Archives/Public/public-geolocation/2011Nov/0016.html
> was the last I heard about the matter I believe.

As per the minutes, we should fire an event for each listener that's added. 
Is my understanding correct? Is this the way other specs (orientation) 
handle this case?


> -- 
> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
> 
Received on Tuesday, 22 May 2012 13:33:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 13:33:30 GMT