public-geolocation@w3.org from February 2016 by date

Friday, 26 February 2016

• Closed: [deviceorientation] Specify the init*Event() methods? Philip Jägenstedt via GitHub
• Closed: [deviceorientation] Spec should include a link for where issues are tracked Tim Volodine via GitHub
• Closed: [deviceorientation] [Callback] extended attributes Tim Volodine via GitHub
• Re: [deviceorientation] Remove the [Callback] extended attribute Tim Volodine via GitHub
• Re: [deviceorientation] Remove the [Callback] extended attribute Philip Jägenstedt via GitHub
• [deviceorientation] Pull Request: Add a Participate section with links to GitHub Philip Jägenstedt via GitHub
• [deviceorientation] Pull Request: Use HTTPS as needed to avoid mixed content warnings Philip Jägenstedt via GitHub
• [deviceorientation] Pull Request: Add missing semicolons to IDL blocks Philip Jägenstedt via GitHub
• [deviceorientation] Pull Request: Remove the [Callback] extended attribute Philip Jägenstedt via GitHub

Thursday, 25 February 2016

• Re: [deviceorientation] [Callback] extended attributes Tim Volodine via GitHub
• Re: [deviceorientation] add security and privacy section Tim Volodine via GitHub
• Re: [deviceorientation] [Callback] extended attributes Philip Jägenstedt via GitHub
• Re: [deviceorientation] Specify the init*Event() methods? Philip Jägenstedt via GitHub
• Re: [deviceorientation] DeviceMotionEventInit interface members Philip Jägenstedt via GitHub

Tuesday, 23 February 2016

• Re: [ServiceWorker] Expose GeoLocation to workers (#745) Richard Maher
• Re: [geofencing-api] Why is geofencing design tied to service workers? Richard Maher via GitHub

Friday, 19 February 2016

• Re: [geofencing-api] Why is geofencing design tied to service workers? Richard Maher via GitHub

Thursday, 18 February 2016

• Re: [deviceorientation] add security and privacy section Maryam Mehrnezhad (PGR)
• Re: [deviceorientation] add security and privacy section maryammjd via GitHub
• Re: [deviceorientation] add security and privacy section Chaals McCathie Nevile

Wednesday, 17 February 2016

• Re: [geofencing-api] Why is geofencing design tied to service workers? Richard Maher via GitHub
• Re: [geolocation] New Working Group Technical Report - Background GPS Richard Maher
• [geolocation] New Working Group Technical Report - Background GPS Richard Maher

Friday, 12 February 2016

• Re: [geofencing-api] Why is geofencing design tied to service workers? Richard Maher via GitHub
• Re: [ServiceWorker] Expose GeoLocation to workers (#745) Richard Maher

Thursday, 11 February 2016

• Re: Mirroring discussion in Github Repo's on public-geo Chaals McCathie Nevile
• Re: Mirroring discussion in Github Repo's on public-geo Martin Thomson
• Re: Mirroring discussion in Github Repo's on public-geo Marijn Kruisselbrink

Wednesday, 10 February 2016

• Re: [ServiceWorker] Expose GeoLocation to workers (#745) Richard Maher
• Re: Mirroring discussion in Github Repo's on public-geo Jeffrey Yasskin
• RE: Mirroring discussion in Github Repo's on public-geo Mandyam, Giridhar
• Re: [deviceorientation] add security and privacy section maryammjd via GitHub
• Re: [deviceorientation] add security and privacy section Martin Thomson via GitHub
• [geofencing-api] An alternative/enhancement to proposed geofencing API Richard Maher
• Re: Mirroring discussion in Github Repo's on public-geo Marcos Caceres

Tuesday, 9 February 2016

• Re: [deviceorientation] add security and privacy section Rich Tibbett via GitHub
• Re: [deviceorientation] add security and privacy section maryammjd via GitHub
• Mirroring discussion in Github Repo's on public-geo Mandyam, Giridhar
• Re: [geofencing-api] Why is geofencing design tied to service workers? Richard Maher via GitHub

Last message date: Friday, 26 February 2016 19:00:41 UTC