Re: [screen-wake-lock] editorial: Add internal slots to WakeLockSentinel. (#280)
Re: [dap-charter] DASWG: Leave System WakeLock API in WICG until there is a second implementer (#101)
Re: [screen-wake-lock] Add WakeLockSentinel.released. (#279)
[system-wake-lock] Privacy consideration about tracking location (#3)
- Re: [system-wake-lock] Privacy consideration about tracking location (#3)
- Re: [system-wake-lock] Privacy consideration about tracking location (#3)
- Re: [system-wake-lock] Privacy consideration about tracking location (#3)
- Re: [system-wake-lock] Privacy consideration about tracking location (#3)
Re: [dap-charter] DASWG: Drop Ambient light sensor API for privacy and lack of implementer support (#100)
- Re: [dap-charter] DASWG: Drop Ambient light sensor API for privacy and lack of implementer support (#100)
- Re: [dap-charter] DASWG: Drop Ambient light sensor API for privacy and lack of implementer support (#100)
Re: [deviceorientation] Drop duplicate PermissionState definition (#88)
[screen-wake-lock] User prompts to show an active screen-lock should have an associated domain (#278)
- Re: [screen-wake-lock] User prompts to show an active screen-lock should have an associated domain (#278)
- Re: [screen-wake-lock] User prompts to show an active screen-lock should have an associated domain (#278)
[screen-wake-lock] Do not use allow="screen-wake-lock" for iframes (#277)
Re: [dap-charter] DASWG: Drop Geolocation Sensor in favor of existing APIs (#103)
[screen-wake-lock] Be able to query if there are any screen wake-lock object active for the current page (#273)
- Re: [screen-wake-lock] Be able to query if there are any screen wake-lock object active for the current page (#273)
- Re: [screen-wake-lock] Be able to query if there are any screen wake-lock object active for the current page (#273)
- Re: [screen-wake-lock] Be able to query if there are any screen wake-lock object active for the current page (#273)
- Re: [screen-wake-lock] Be able to query if there are any screen wake-lock object active for the current page (#273)
- Re: [screen-wake-lock] Be able to query if there are any screen wake-lock object active for the current page (#273)
- Re: [screen-wake-lock] Be able to query if there are any screen wake-lock object active for the current page (#273)
[screen-wake-lock] sentinel.released boolean (#272)
- Re: [screen-wake-lock] sentinel.released boolean (#272)
- Re: [screen-wake-lock] sentinel.released boolean (#272)
- Re: [screen-wake-lock] sentinel.released boolean (#272)
- Re: [screen-wake-lock] sentinel.released boolean (#272)
- Re: [screen-wake-lock] sentinel.released boolean (#272)
- Closed: [screen-wake-lock] sentinel.released boolean (#272)
[screen-wake-lock] release() linking to wrong algorithm? (#271)
Re: [geolocation-api] How to specify desired accuracy / resolution of data? (#49)
Re: [geolocation-api] [meta] Wide review tracker (#43)
Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
[geolocation-api] Security review: General observations (#57)
- Re: [geolocation-api] Security review: General observations (#57)
- Re: [geolocation-api] Security review: General observations (#57)
[geolocation-api] Sectioni 6: Non-normative but 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)
[geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
- Re: [geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
- Re: [geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
- Closed: [geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
[geolocation-api] 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] Editorial - possible syntax error (#53)
- Re: [geolocation-api] Section 1: Editorial - possible syntax error (#53)
- Closed: [geolocation-api] Section 1: Editorial - possible syntax error (#53)
Re: [screen-wake-lock] Privacy consideration about tracking location (#137)
- Re: [screen-wake-lock] Privacy consideration about tracking location (#137)
- Re: [screen-wake-lock] Privacy consideration about tracking location (#137)
Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
[screen-wake-lock] [meta] Wide review tracker (#270)
Re: [geolocation-api] Editorial: fix up .message text (#51)
Re: [screen-wake-lock] Add a Changes section (#269)
Re: [screen-wake-lock] Publish a new Candidate Recommendation (#262)
Re: [screen-wake-lock] New shortname (#257)
Closed: [screen-wake-lock] Add "geolocation" wake lock (#170)
Re: [screen-wake-lock] Add "geolocation" wake lock (#170)
- Re: [screen-wake-lock] Add "geolocation" wake lock (#170)
- Re: [screen-wake-lock] Add "geolocation" wake lock (#170)
Closed: [screen-wake-lock] Update the reference to Feature Policy (#264)
[screen-wake-lock] Set up ReSpec autopublish (#268)
- Re: [screen-wake-lock] Set up ReSpec autopublish (#268)
- Closed: [screen-wake-lock] Set up ReSpec autopublish (#268)
- Re: [screen-wake-lock] Set up ReSpec autopublish (#268)
Re: [screen-wake-lock] Editorial: s/Feature Policy/Permissions Policy (#266)
Re: [dap-charter] DASWG: Drop Generic Sensor API (#106)
Re: [geolocation-api] Explicitly limit permission lifetimes (#47)
Re: [dap-charter] DASWG: Drop Battery API for privacy and lack of implementer support (#98)
- Re: [dap-charter] DASWG: Drop Battery API for privacy and lack of implementer support (#98)
- Re: [dap-charter] DASWG: Drop Battery API for privacy and lack of implementer support (#98)
- Re: [dap-charter] DASWG: Drop Battery API for privacy and lack of implementer support (#98)
- Re: [dap-charter] DASWG: Drop Battery API for privacy and lack of implementer support (#98)
- Re: [dap-charter] DASWG: Drop Battery API for privacy and lack of implementer support (#98)