Re: [screen-wake-lock] editorial: Remove the "state record" concept. (#312)
Re: [geolocation-api] Publish as FPWD (#42)
Re: [accelerometer] Add a Permissions Policy Integration section (#60)
Closed: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
Re: [geolocation-api] Hook into Permissions API to get permission (#68)
Re: [geolocation-api] Editorial: recipients are not a conformance class (#66)
Closed: [geolocation-api] Add explainer to the spec repo (#59)
Re: [screen-wake-lock] Auto-releasing wake lock depending on the user presence (#300)
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)
Re: [geolocation-api] Republish REC? (#42)
- Re: [geolocation-api] Republish REC? (#42)
- Re: [geolocation-api] Republish REC? (#42)
- Re: [geolocation-api] Republish REC? (#42)
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)
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] 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: [screen-wake-lock] Clean up task queuing and document management (#307)
Closed: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
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)
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)
Closed: [geolocation-api] errorCallback parameter to getPosition() and watchPosition() is nullable in all major browser engines (#61)
Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299)
- Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299)
- Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299)
- Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299)
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)
Closed: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
[device-posture] Rename "posture modes" to "posture types" (#64)
- Closed: [device-posture] Rename "posture modes" to "posture types" (#64)
- Re: [device-posture] Rename "posture modes" to "posture types" (#64)
- Re: [device-posture] Rename "posture modes" to "posture types" (#64)
- Re: [device-posture] Rename "posture modes" to "posture types" (#64)
[device-posture] Adding fold position to identify orientation instead of identify device model (#63)
Re: [device-posture] Definition for "posture" missing (#59)
Re: [device-posture] Fixes after renaming. (#62)
Re: [device-posture] Rename the spec (#61)
Re: [screen-wake-lock] shouldn't this be part of the permissions API? (#59)
- Re: [screen-wake-lock] shouldn't this be part of the permissions API? (#59)
- Re: [screen-wake-lock] shouldn't this be part of the permissions API? (#59)
Re: [html-media-capture] Upstream HTML Media Capture to HTML? (#28)
[sensors] IR sender/receiver #957 (#409)
Re: [screen-wake-lock] editorial: Remove the "obtain a permission" algorithm. (#298)
Re: [dap-charter] Contact Picker API (#97)
- Re: [dap-charter] Contact Picker API (#97)
- Re: [dap-charter] Contact Picker API (#97)
- Re: [dap-charter] Contact Picker API (#97)
- Re: [dap-charter] Contact Picker API (#97)