- From: Ayumi Hamasaki via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 May 2016 20:44:33 +0000
- To: public-geolocation@w3.org
ayumihamsaki has just created a new issue for https://github.com/w3c/geofencing-api: == Uncaught (in promise) ReferenceError: CircularGeofenceRegion is not defined == Hi maybe it's me but I am getting this error with the example on w3C and on our test script, I will give you the script where the error is coming from with the w3C example: ``` // https://example.com/webapp.js navigator.serviceWorker .register('serviceworker.js') .then((swRegistration) => { let region = new CircularGeofenceRegion({ name: 'myfence', latitude: 37.421999, longitude: -122.084015, radius: 1000 }); let options = { includePosition: true }; swRegistration.geofencing.add(region, options) .then( // If more than just a name needs to be stored with a geofence, now // would be the time to store this in some storage. (geofence) => console.log(geofence.id), (error) => console.log(error) ); }); ``` I am getting this error in Google Canary Version 52.0.2727.0 canary (64-bit). I hope someone can help as very keen to combine geofencing to my service worker script. Please view or discuss this issue at https://github.com/w3c/geofencing-api/issues/27 using your GitHub account
Received on Saturday, 7 May 2016 20:44:35 UTC