public-device-apis-log@w3.org from February 2021 by author

Andy Carle via GitHub

Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Friday, 5 February)

Anne van Kesteren via GitHub

Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306) (Wednesday, 24 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Thursday, 11 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Thursday, 11 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Tuesday, 2 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Tuesday, 2 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)

Anssi Kostiainen via GitHub

Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Friday, 26 February)
Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Friday, 26 February)
Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Thursday, 25 February)
Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Thursday, 25 February)
Closed: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58) (Tuesday, 23 February)
Re: [accelerometer] Note gravity and linear accelerometer relationship (#59) (Tuesday, 23 February)
Re: [proximity] https://w3c.github.io/proximity/ not updated (#45) (Tuesday, 16 February)
Closed: [proximity] https://w3c.github.io/proximity/ not updated (#45) (Tuesday, 16 February)
Re: [proximity] Regenerate HTML snapshot to trigger rebuild (#46) (Tuesday, 16 February)
Re: [orientation-sensor] fix: img width/height percentages to style (#69) (Thursday, 11 February)
Re: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58) (Tuesday, 9 February)
[screen-wake-lock] Auto-releasing wake lock depending on the user presence (#300) (Friday, 5 February)
Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Friday, 5 February)

Domenic Denicola via GitHub

Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Friday, 26 February)
Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Thursday, 25 February)
Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Thursday, 25 February)
Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Thursday, 25 February)
Re: [screen-wake-lock] Clean up task queuing and document management (#307) (Thursday, 25 February)
Re: [screen-wake-lock] Clean up task queuing and document management (#307) (Wednesday, 24 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Tuesday, 2 February)

Jeffrey Yasskin via GitHub

Re: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58) (Tuesday, 9 February)
[accelerometer] Explain how the implementation separates gravity from linear acceleration (#58) (Tuesday, 9 February)

Kenneth Rohde Christiansen via GitHub

Re: [screen-wake-lock] editorial: Simplify the "obtain permission" algorithm. (#303) (Wednesday, 10 February)

Marcos Cáceres via GitHub

Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306) (Wednesday, 24 February)
Re: [dap-charter] Contact Picker API (#97) (Wednesday, 24 February)
Re: [screen-wake-lock] editorial: Remove the "obtain a permission" algorithm. (#298) (Wednesday, 17 February)

Mounir Lamouri via GitHub

Closed: [battery] Update the reference to Feature Policy (#26) (Friday, 26 February)

Philip Jägenstedt via GitHub

Re: [proximity] https://w3c.github.io/proximity/ not updated (#45) (Tuesday, 16 February)
[proximity] https://w3c.github.io/proximity/ not updated (#45) (Monday, 15 February)

Raphael Kubo da Costa via GitHub

Re: [screen-wake-lock] Clean up task queuing and document management (#307) (Thursday, 25 February)
Re: [screen-wake-lock] Clean up task queuing and document management (#307) (Thursday, 25 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Thursday, 25 February)
Re: [screen-wake-lock] Clean up task queuing and document management (#307) (Wednesday, 24 February)
Re: [screen-wake-lock] Clean up task queuing and document management (#307) (Wednesday, 24 February)
Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306) (Wednesday, 24 February)
Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306) (Monday, 22 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Monday, 15 February)
Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306) (Monday, 15 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Thursday, 11 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Thursday, 11 February)
Closed: [screen-wake-lock] obtain permission seems wrong (#187) (Thursday, 11 February)
Re: [screen-wake-lock] editorial: Simplify the "obtain permission" algorithm. (#303) (Wednesday, 10 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Monday, 8 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Saturday, 6 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Friday, 5 February)
Re: [screen-wake-lock] editorial: Formally define a permission revocation algorithm. (#297) (Friday, 5 February)
Re: [screen-wake-lock] editorial: Formally define a permission revocation algorithm. (#297) (Thursday, 4 February)
Re: [screen-wake-lock] editorial: Formally define a permission revocation algorithm. (#297) (Thursday, 4 February)
Re: [screen-wake-lock] Adjust state record selection in "Managing Wake Locks". (#295) (Thursday, 4 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Tuesday, 2 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Tuesday, 2 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)
Re: [screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)
[screen-wake-lock] "Release a wake lock": should we queue a task to fire the "release" event? (#293) (Monday, 1 February)

Reilly Grant via GitHub

Re: [battery] Assess compatibility risk of using [SecureContext] (#15) (Friday, 26 February)
Re: [dap-charter] Contact Picker API (#97) (Wednesday, 24 February)
Re: [screen-wake-lock] editorial: Improve references to terms from the Page Visibility spec. (#306) (Wednesday, 24 February)
Re: [accelerometer] Explain how the implementation separates gravity from linear acceleration (#58) (Tuesday, 9 February)
Re: [screen-wake-lock] editorial: Tidy up uses of "in parallel". (#299) (Friday, 5 February)

W3C Bot via GitHub

Re: [orientation-sensor] fix: img width/height percentages to style (#69) (Thursday, 11 February)

Last message date: Friday, 26 February 2021 19:50:40 UTC