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

Addison Phillips via GitHub

• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Wednesday, 28 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Wednesday, 7 April)

Alexis Menard via GitHub

• Re: [device-posture] Rename word "mode" in the posture definition to "type". (#68) (Thursday, 29 April)
• Re: [device-posture] Rename word "mode" in the posture definition to "type". (#68) (Thursday, 29 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Thursday, 29 April)
• Re: [device-posture] Move the entry point of the API to the window.navigator interface. (#71) (Thursday, 29 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Monday, 26 April)
• Re: [device-posture] Adding posture definition and clarification (#69) (Monday, 26 April)
• Re: [device-posture] Rename word "mode" in the posture definition to "type". (#68) (Thursday, 22 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Thursday, 22 April)
• [device-posture] Move the posture object out of the Screen interface. (#67) (Thursday, 22 April)
• Re: [device-posture] Rename "posture modes" to "posture types" (#64) (Thursday, 22 April)

Anssi Kostiainen via GitHub

• Re: [device-posture] Switch to w3c/spec-prod to automate publication to /TR (#72) (Friday, 30 April)
• Re: [device-posture] update affiliation for Diego (#52) (Thursday, 29 April)
• Re: [device-posture] Adding posture definition and clarification (#69) (Thursday, 29 April)
• Closed: [device-posture] Rename "posture modes" to "posture types" (#64) (Thursday, 29 April)
• Re: [device-posture] Rename word "mode" in the posture definition to "type". (#68) (Thursday, 29 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Thursday, 29 April)
• Re: [dap-charter] Compute Pressure API (#111) (Tuesday, 27 April)
• Re: [geolocation-api] Publish as FPWD (#42) (Tuesday, 27 April)
• Re: [dap-charter] Compute Pressure API (#111) (Monday, 26 April)
• Re: [ambient-light] Request for Ambient Light Sensor web developer feedback (#64) (Friday, 23 April)
• Re: [geolocation-api] Publish as FPWD (#42) (Monday, 12 April)
• Re: [system-wake-lock] Use case: Simulations, rendering and creative coding (#7) (Friday, 9 April)
• Re: [geolocation-api] Explicitly limit permission lifetimes (#69) (Wednesday, 7 April)
• Re: [screen-wake-lock] Auto-releasing wake lock depending on the user presence (#300) (Tuesday, 6 April)

Becky Gibson via GitHub

• [device-posture] Requesting Accessibility Considerations section (#70) (Wednesday, 28 April)

Carlos Lopez via GitHub

• Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22) (Wednesday, 14 April)

Daniel Hensby via GitHub

• Re: [screen-wake-lock] Need maximum screen brightness mode (#129) (Monday, 12 April)

Domenic Denicola via GitHub

• Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Thursday, 8 April)

François Beaufort via GitHub

• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Monday, 26 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Monday, 26 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Monday, 26 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Monday, 26 April)

Fuqiao Xue via GitHub

• Re: [device-posture] Adding posture definition and clarification (#69) (Friday, 30 April)
• Re: [dap-charter] Compute Pressure API (#111) (Wednesday, 28 April)
• Re: [geolocation-api] Broken link (#70) (Wednesday, 28 April)
• [geolocation-api] Broken fragments (#71) (Wednesday, 28 April)
• [geolocation-api] Broken link (#70) (Wednesday, 28 April)
• Re: [dap-charter] Compute Pressure API (#111) (Tuesday, 27 April)
• Re: [dap-charter] Compute Pressure API (#111) (Tuesday, 27 April)
• Re: [dap-charter] Idle Detection API (#110) (Saturday, 17 April)
• [dap-charter] Idle Detection API (#110) (Saturday, 17 April)
• Re: [geolocation-api] Publish as FPWD (#42) (Monday, 12 April)
• Re: [dap-charter] Contact Picker API (#97) (Tuesday, 6 April)

Jake Archibald via GitHub

• Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22) (Thursday, 15 April)

Jaume Sanchez via GitHub

• [system-wake-lock] Use case: Simulations, rendering and creative coding (#7) (Friday, 9 April)

Johann Hofmann via GitHub

• Re: [geolocation-api] Restrict to user-activation-received frames (#48) (Wednesday, 7 April)

Kenneth Rohde Christiansen via GitHub

• Closed: [device-posture] Move the posture object out of the Screen interface. (#67) (Friday, 30 April)
• Re: [device-posture] Adding posture definition and clarification (#69) (Thursday, 29 April)
• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Friday, 23 April)
• Re: [device-posture] Rename "posture modes" to "posture types" (#64) (Thursday, 22 April)
• Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Thursday, 8 April)

Lars Knudsen via GitHub

• Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Thursday, 8 April)

Laszlo Gombos via GitHub

• Re: [device-posture] Definition for "posture" missing (#59) (Tuesday, 6 April)

Laura via GitHub

• Re: [device-posture] Move the posture object out of the Screen interface. (#67) (Friday, 23 April)

Marcos Cáceres via GitHub

• Re: [geolocation-api] Broken fragments (#71) (Thursday, 29 April)
• Re: [geolocation-api] Broken fragments (#71) (Thursday, 29 April)
• Re: [geolocation-api] Broken link (#70) (Thursday, 29 April)
• Re: [geolocation-api] Broken link (#70) (Thursday, 29 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Thursday, 29 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Thursday, 29 April)
• Closed: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Wednesday, 28 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Wednesday, 28 April)
• Re: [geolocation-api] Publish as FPWD (#42) (Monday, 12 April)
• Re: [geolocation-api] Publish as FPWD (#42) (Friday, 9 April)
• Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Thursday, 8 April)
• Re: [geolocation-api] Restrict to user-activation-received frames (#48) (Thursday, 8 April)
• Re: [geolocation-api] Explicitly limit permission lifetimes (#69) (Thursday, 8 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Thursday, 8 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Thursday, 8 April)
• Closed: [geolocation-api] Explicitly limit permission lifetimes (#69) (Wednesday, 7 April)
• Re: [geolocation-api] Explicitly limit permission lifetimes (#69) (Wednesday, 7 April)
• Re: [geolocation-api] Restrict to user-activation-received frames (#48) (Tuesday, 6 April)
• Re: [geolocation-api] Restrict access to visible and user-activation-received frames (#48) (Saturday, 3 April)
• Closed: [geolocation-api] How to specify desired accuracy / resolution of data? (#49) (Saturday, 3 April)
• Re: [geolocation-api] How to specify desired accuracy / resolution of data? (#49) (Saturday, 3 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Saturday, 3 April)
• Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50) (Friday, 2 April)
• Re: [geolocation-api] Restrict access to visible and user-activation-received frames (#48) (Friday, 2 April)
• Closed: [geolocation-api] Restrict access to visible and user-activation-received frames (#48) (Friday, 2 April)
• Re: [geolocation-api] How to specify desired accuracy / resolution of data? (#49) (Friday, 2 April)

Martin Thomson via GitHub

• Re: [geolocation-api] Restrict to user-activation-received frames (#48) (Wednesday, 7 April)

Olivier Yiptong via GitHub

• [dap-charter] Compute Pressure API (#111) (Monday, 26 April)

pes via GitHub

• Re: [geolocation-api] Explicitly limit permission lifetimes (#69) (Monday, 12 April)
• Re: [geolocation-api] Restrict access to visible and user-activation-received frames (#48) (Tuesday, 6 April)
• [geolocation-api] Explicitly limit permission lifetimes (#69) (Saturday, 3 April)
• Re: [geolocation-api] Restrict access to visible and user-activation-received frames (#48) (Friday, 2 April)

Raphael Kubo da Costa via GitHub

• Closed: [screen-wake-lock] Auto-releasing wake lock depending on the user presence (#300) (Monday, 5 April)

Reilly Grant via GitHub

• Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Thursday, 8 April)
• Re: [proximity] Behavior of `distance` attribute when sensor cannot provide distance measurements? (#44) (Thursday, 8 April)
• Re: [geolocation-api] Restrict to user-activation-received frames (#48) (Thursday, 8 April)

Will Morgan via GitHub

• Re: [screen-wake-lock] Need maximum screen brightness mode (#129) (Saturday, 10 April)
• Re: [ambient-light] Request for Ambient Light Sensor web developer feedback (#64) (Saturday, 10 April)

Last message date: Friday, 30 April 2021 16:45:45 UTC