Anssi Kostiainen via GitHub
Chris Dumez via GitHub
Fuqiao Xue via GitHub
magnus-git via GitHub
Marcos Cáceres via GitHub
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Monday, 29 March)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Sunday, 28 March)
- Re: [geolocation-api] Only update position if document is showing (#67) (Thursday, 25 March)
- Re: [geolocation-api] Publish as FPWD (#42) (Thursday, 25 March)
- Re: [geolocation-api] Only update position if document is showing (#67) (Thursday, 25 March)
- Closed: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) (Thursday, 25 March)
- Re: [geolocation-api] Hook into Permissions API to get permission (#68) (Thursday, 25 March)
- Re: [geolocation-api] MUST have express permission to share location (#64) (Wednesday, 24 March)
- Re: [geolocation-api] Only update position if document is showing (#67) (Wednesday, 24 March)
- Re: [geolocation-api] Only update position if document is showing (#67) (Wednesday, 24 March)
- Re: [geolocation-api] Editorial: recipients are not a conformance class (#66) (Wednesday, 24 March)
- Closed: [geolocation-api] Add explainer to the spec repo (#59) (Tuesday, 23 March)
- Re: [geolocation-api] Republish REC? (#42) (Tuesday, 23 March)
- Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65) (Tuesday, 23 March)
- Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65) (Tuesday, 23 March)
- Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65) (Tuesday, 23 March)
- Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56) (Tuesday, 23 March)
- Re: [geolocation-api] Republish REC? (#42) (Tuesday, 23 March)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) (Tuesday, 23 March)
- Re: [geolocation-api] Republish REC? (#42) (Tuesday, 23 March)
- Re: [geolocation-api] MUST have express permission to share location (#64) (Tuesday, 23 March)
- [geolocation-api] Pull Request: Hook into Permissions API to get permission (Tuesday, 23 March)
- Closed: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56) (Tuesday, 23 March)
- Re: [geolocation-api] Explicitly limit permission lifetimes (#47) (Tuesday, 23 March)
- Re: [geolocation-api] Explicitly limit permission lifetimes (#47) (Tuesday, 23 March)
- Re: [geolocation-api] Only update position if document is showing (#67) (Tuesday, 23 March)
- [geolocation-api] Pull Request: Only update position if document is showing (Tuesday, 23 March)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) (Tuesday, 23 March)
- Closed: [geolocation-api] Security review: General observations (#57) (Tuesday, 23 March)
- Re: [geolocation-api] Security review: General observations (#57) (Tuesday, 23 March)
- Re: [geolocation-api] Explicitly limit permission lifetimes (#47) (Monday, 22 March)
- Closed: [geolocation-api] Explicitly limit permission lifetimes (#47) (Monday, 22 March)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Monday, 22 March)
- [geolocation-api] Pull Request: Editorial: recipients are not a conformance class (Monday, 22 March)
- [geolocation-api] Pull Request: Editorial: call out examples more clearly + add explainer (Monday, 22 March)
- [geolocation-api] Pull Request: MUST have express permission to share location (Monday, 22 March)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54) (Monday, 22 March)
- [geolocation-api] Pull Request: Editorial: remove RFC2119 words from Requirements (Monday, 22 March)
- Re: [geolocation-api] Default errorCallback to null (#62) (Monday, 22 March)
- Re: [geolocation-api] Default errorCallback to null (#62) (Monday, 22 March)
- Re: [geolocation-api] Default errorCallback to null (#62) (Monday, 22 March)
- Closed: [geolocation-api] errorCallback parameter to getPosition() and watchPosition() is nullable in all major browser engines (#61) (Monday, 22 March)
- Re: [geolocation-api] Default errorCallback to null (#62) (Wednesday, 17 March)
- [geolocation-api] Pull Request: Default errorCallback to null (Wednesday, 17 March)
- Closed: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Wednesday, 17 March)
pes via GitHub
r12a via GitHub
Reilly Grant via GitHub
Samuel Weiler via GitHub
Last message date: Monday, 29 March 2021 00:51:34 UTC