Re: [geofencing-api] Uncaught (in promise) ReferenceError: CircularGeofenceRegion is not defined

A victory for common sense. Excellent news!

On Thu, May 12, 2016 at 2:40 AM, Marijn Kruisselbrink <mek@chromium.org>
 wrote:

> For quite a while now the geofencing API hasn't been much of a priority
> for us. Now in addition to that we're no longer convinced the geofencing
> API in its current shape is the best way to address the use cases we're
> interested in addressing. So with that in mind we've decided to stop work
> on the geofencing API in its current form.
>
> Marijn
>

Combine that outcome with this at the upcoming TPAC: -

Hello All,

The registration for TPAC 2016 is now open - relevant information is
provided in the email attachment below.  There will not be a stand-alone
meeting for the Geolocation Working Group, but there will likely be a joint
meeting between the Geo WG and the Devices and Sensors (DAS) WG.  This
should be confirmed soon, and will take place during the DAS WG's allocated
meeting time (Sep. 19-20).

Thanks,

-Giri Mandyam, Geolocation Working Group Chair

An the scene is set for a ServiceWorker.TravelManager.subscribe() outcome
or, more likely, a generic sensor.AddListener(filterOptions). Either way
these are exciting times indeed. Good Luck!

On Mon, May 9, 2016 at 12:59 AM, Ayumi Hamasaki via GitHub <sysbot+gh@w3.org
> wrote:

> Thanks for the reply. Will wait for implementation.
>
> --
> GitHub Notification of comment by ayumihamsaki
> Please view or discuss this issue at
> https://github.com/w3c/geofencing-api/issues/27#issuecomment-217732924
>  using your GitHub account
>
>