public-geolocation@w3.org from March 2021 by date

Monday, 29 March 2021

• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) Marcos Cáceres via GitHub
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) Fuqiao Xue via GitHub

Sunday, 28 March 2021

• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) Marcos Cáceres via GitHub

Friday, 26 March 2021

• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) r12a via GitHub
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) Fuqiao Xue via GitHub

Thursday, 25 March 2021

• Re: [geolocation-api] Only update position if document is showing (#67) Marcos Cáceres via GitHub
• Re: [geolocation-api] Publish as FPWD (#42) Marcos Cáceres via GitHub
• Re: [geolocation-api] Only update position if document is showing (#67) Reilly Grant via GitHub
• Re: [geolocation-api] Hook into Permissions API to get permission (#68) Reilly Grant via GitHub
• Re: [geolocation-api] Only update position if document is showing (#67) Marcos Cáceres via GitHub
• Closed: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) Marcos Cáceres via GitHub
• Re: [geolocation-api] Hook into Permissions API to get permission (#68) Marcos Cáceres via GitHub

Wednesday, 24 March 2021

• Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56) magnus-git via GitHub
• Re: [geolocation-api] MUST have express permission to share location (#64) Marcos Cáceres via GitHub
• Re: [geolocation-api] Only update position if document is showing (#67) Marcos Cáceres via GitHub
• Re: [geolocation-api] Only update position if document is showing (#67) Marcos Cáceres via GitHub
• Re: [geolocation-api] Editorial: recipients are not a conformance class (#66) Marcos Cáceres via GitHub

Tuesday, 23 March 2021

• Closed: [geolocation-api] Add explainer to the spec repo (#59) Marcos Cáceres via GitHub
• Re: [geolocation-api] Republish REC? (#42) Marcos Cáceres via GitHub
• Re: [geolocation-api] Republish REC? (#42) Anssi Kostiainen via GitHub
• Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65) Marcos Cáceres via GitHub
• Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65) Marcos Cáceres via GitHub
• Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65) Marcos Cáceres via GitHub
• Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56) Marcos Cáceres via GitHub
• Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56) magnus-git via GitHub
• Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65) Fuqiao Xue via GitHub
• Re: [geolocation-api] Republish REC? (#42) Marcos Cáceres via GitHub
• Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) Marcos Cáceres via GitHub
• Re: [geolocation-api] Republish REC? (#42) Marcos Cáceres via GitHub
• Re: [geolocation-api] MUST have express permission to share location (#64) Marcos Cáceres via GitHub
• [geolocation-api] Pull Request: Hook into Permissions API to get permission Marcos Cáceres via GitHub
• Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56) Samuel Weiler via GitHub
• Closed: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56) Marcos Cáceres via GitHub
• Re: [geolocation-api] Explicitly limit permission lifetimes (#47) Marcos Cáceres via GitHub
• Re: [geolocation-api] Explicitly limit permission lifetimes (#47) Marcos Cáceres via GitHub
• Re: [geolocation-api] Only update position if document is showing (#67) Marcos Cáceres via GitHub
• [geolocation-api] Pull Request: Only update position if document is showing Marcos Cáceres via GitHub
• Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) Marcos Cáceres via GitHub
• Closed: [geolocation-api] Security review: General observations (#57) Marcos Cáceres via GitHub
• Re: [geolocation-api] Security review: General observations (#57) Marcos Cáceres via GitHub

Monday, 22 March 2021

• Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) Reilly Grant via GitHub
• Re: [geolocation-api] Explicitly limit permission lifetimes (#47) Reilly Grant via GitHub
• Re: [geolocation-api] MUST have express permission to share location (#64) Reilly Grant via GitHub
• Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) Reilly Grant via GitHub
• Re: [geolocation-api] Explicitly limit permission lifetimes (#47) pes via GitHub
• Re: [geolocation-api] Explicitly limit permission lifetimes (#47) Marcos Cáceres via GitHub
• Closed: [geolocation-api] Explicitly limit permission lifetimes (#47) Marcos Cáceres via GitHub
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) Marcos Cáceres via GitHub
• [geolocation-api] Pull Request: Editorial: recipients are not a conformance class Marcos Cáceres via GitHub
• [geolocation-api] Pull Request: Editorial: call out examples more clearly + add explainer Marcos Cáceres via GitHub
• [geolocation-api] Pull Request: MUST have express permission to share location Marcos Cáceres via GitHub
• Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) Marcos Cáceres via GitHub
• [geolocation-api] Pull Request: Editorial: remove RFC2119 words from Requirements Marcos Cáceres via GitHub
• Re: [geolocation-api] Default errorCallback to null (#62) Marcos Cáceres via GitHub
• Re: [geolocation-api] Default errorCallback to null (#62) Chris Dumez via GitHub
• Re: [geolocation-api] Default errorCallback to null (#62) Marcos Cáceres via GitHub
• Re: [geolocation-api] Default errorCallback to null (#62) Marcos Cáceres via GitHub
• Closed: [geolocation-api] errorCallback parameter to getPosition() and watchPosition() is nullable in all major browser engines (#61) Marcos Cáceres via GitHub

Wednesday, 17 March 2021

• Re: [geolocation-api] Default errorCallback to null (#62) Marcos Cáceres via GitHub
• [geolocation-api] Pull Request: Default errorCallback to null Marcos Cáceres via GitHub
• Closed: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) Marcos Cáceres via GitHub

Last message date: Monday, 29 March 2021 00:51:34 UTC