Re: [geolocation-api] Publish as FPWD (#42)
Closed: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
Closed: [geolocation-api] Add explainer to the spec repo (#59)
Re: [geolocation-api] Republish REC? (#42)
- Re: [geolocation-api] Republish REC? (#42)
- Re: [geolocation-api] Republish REC? (#42)
- Re: [geolocation-api] Republish REC? (#42)
[geolocation-api] Pull Request: Hook into Permissions API to get permission
- Re: [geolocation-api] Hook into Permissions API to get permission (#68)
- Re: [geolocation-api] Hook into Permissions API to get permission (#68)
Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56)
- Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56)
- Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56)
- Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56)
Closed: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56)
[geolocation-api] Pull Request: Only update position if document is showing
- Re: [geolocation-api] Only update position if document is showing (#67)
- Re: [geolocation-api] Only update position if document is showing (#67)
- Re: [geolocation-api] Only update position if document is showing (#67)
- Re: [geolocation-api] Only update position if document is showing (#67)
- Re: [geolocation-api] Only update position if document is showing (#67)
- Re: [geolocation-api] Only update position if document is showing (#67)
Closed: [geolocation-api] Security review: General observations (#57)
Re: [geolocation-api] Security review: General observations (#57)
Re: [geolocation-api] Explicitly limit permission lifetimes (#47)
- Re: [geolocation-api] Explicitly limit permission lifetimes (#47)
- Re: [geolocation-api] Explicitly limit permission lifetimes (#47)
- Re: [geolocation-api] Explicitly limit permission lifetimes (#47)
- Re: [geolocation-api] Explicitly limit permission lifetimes (#47)
Closed: [geolocation-api] Explicitly limit permission lifetimes (#47)
Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
[geolocation-api] Pull Request: Editorial: recipients are not a conformance class
[geolocation-api] Pull Request: Editorial: call out examples more clearly + add explainer
- Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65)
- Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65)
- Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65)
- Re: [geolocation-api] Editorial: call out examples more clearly + add explainer (#65)
[geolocation-api] Pull Request: MUST have express permission to share location
- Re: [geolocation-api] MUST have express permission to share location (#64)
- Re: [geolocation-api] MUST have express permission to share location (#64)
- Re: [geolocation-api] MUST have express permission to share location (#64)
Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
[geolocation-api] Pull Request: Editorial: remove RFC2119 words from Requirements
Closed: [geolocation-api] errorCallback parameter to getPosition() and watchPosition() is nullable in all major browser engines (#61)
[geolocation-api] Pull Request: Default errorCallback to null
- Re: [geolocation-api] Default errorCallback to null (#62)
- Re: [geolocation-api] Default errorCallback to null (#62)
- Re: [geolocation-api] Default errorCallback to null (#62)
- Re: [geolocation-api] Default errorCallback to null (#62)
- Re: [geolocation-api] Default errorCallback to null (#62)