Closed: [battery] Update the reference to Feature Policy (#26)
Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
- Re: [battery] Assess compatibility risk of using [SecureContext] (#15)
Re: [screen-wake-lock] Clean up task queuing and document management (#307)
- Re: [screen-wake-lock] Clean up task queuing and document management (#307)
- Re: [screen-wake-lock] Clean up task queuing and document management (#307)
- Re: [screen-wake-lock] Clean up task queuing and document management (#307)
- Re: [screen-wake-lock] Clean up task queuing and document management (#307)
- Re: [screen-wake-lock] Clean up task queuing and document management (#307)
Re: [dap-charter] Contact Picker API (#97)
Re: [accelerometer] Note gravity and linear accelerometer relationship (#59)
Re: [screen-wake-lock] editorial: Remove the "obtain a permission" algorithm. (#298)
Re: [proximity] Regenerate HTML snapshot to trigger rebuild (#46)
[proximity] https://w3c.github.io/proximity/ not updated (#45)
- Closed: [proximity] https://w3c.github.io/proximity/ not updated (#45)
- Re: [proximity] https://w3c.github.io/proximity/ not updated (#45)
- Re: [proximity] https://w3c.github.io/proximity/ not updated (#45)
Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306)
- Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306)
- Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306)
- Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306)
- Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306)
- Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306)
Re: [orientation-sensor] fix: img width/height percentages to style (#69)
Closed: [screen-wake-lock] obtain permission seems wrong (#187)
Re: [screen-wake-lock] editorial: Simplify the "obtain permission" algorithm. (#303)
[accelerometer] Explain how the implementation separates gravity from linear acceleration (#58)
- Re: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58)
- Re: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58)
- Re: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58)
- Closed: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58)
[screen-wake-lock] Auto-releasing wake lock depending on the user presence (#300)
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: [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: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299)
- Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299)
Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44)
Re: [screen-wake-lock] editorial: Formally define a permission revocation algorithm. (#297)
- Re: [screen-wake-lock] editorial: Formally define a permission revocation algorithm. (#297)
- Re: [screen-wake-lock] editorial: Formally define a permission revocation algorithm. (#297)
Re: [screen-wake-lock] Adjust state record selection in "Managing Wake Locks". (#295)
[screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)
- Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293)