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

Addison Phillips via GitHub

• Re: [compute-pressure] Internationalization Checklist (#184) (Tuesday, 7 February)

Anssi Kostiainen via GitHub

• Re: [compute-pressure] Focus control in privacy test steps (#185) (Tuesday, 14 February)
• Re: [ambient-light] Drop own powerful feature, require active local video source. (#83) (Wednesday, 8 February)
• Re: [compute-pressure] Internationalization Checklist (#184) (Tuesday, 7 February)
• Re: [compute-pressure] Wide review tracker (#177) (Tuesday, 7 February)
• Re: [compute-pressure] Internationalization Checklist (#184) (Tuesday, 7 February)
• [compute-pressure] Internationalization Checklist (#184) (Tuesday, 7 February)
• Re: [contact-picker] Editorial: Add Contacts API history note (#58) (Monday, 6 February)
• Re: [compute-pressure] Accessibility Checklist (#183) (Friday, 3 February)
• [compute-pressure] Accessibility Checklist (#183) (Friday, 3 February)
• Re: [battery] Add Energy Saver Mode explainer (#55) (Friday, 3 February)
• Re: [compute-pressure] Add an implementation-defined change threshold exceeded check (#180) (Thursday, 2 February)
• [compute-pressure] Contributing factors definition needs clarification (#181) (Thursday, 2 February)
• Re: [compute-pressure] Add an implementation-defined change threshold exceeded check (#180) (Wednesday, 1 February)
• Re: [compute-pressure] Add an implementation-defined change threshold exceeded check (#176) (Wednesday, 1 February)
• Re: [compute-pressure] Add hysteresis to notify pressure observers algorithm (#176) (Wednesday, 1 February)
• [device-posture] Avoid using the page visibility change steps hook (#103) (Wednesday, 1 February)

Arnaud (Arno) Mandy via GitHub

• Re: [compute-pressure] Focus control in privacy test steps (#185) (Thursday, 9 February)

Christian Liebel via GitHub

• Closed: [contact-picker] Copyright (#62) (Monday, 20 February)

himorin / Atsushi Shimono via GitHub

• [compute-pressure] missing link in security and privacy section (#186) (Monday, 20 February)
• Re: [compute-pressure] Internationalization Checklist (#184) (Tuesday, 7 February)

Kenneth Rohde Christiansen via GitHub

• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Thursday, 16 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Thursday, 16 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Wednesday, 15 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Wednesday, 15 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Wednesday, 15 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Tuesday, 14 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Monday, 13 February)
• Re: [compute-pressure] Internationalization Checklist (#184) (Tuesday, 7 February)
• Closed: [compute-pressure] Add an implementation-defined change threshold exceeded check (#176) (Thursday, 2 February)

leonixyz via GitHub

• [system-wake-lock] Use case: playback of a list of audio tracks (#14) (Thursday, 2 February)

Marcos Cáceres via GitHub

• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Wednesday, 22 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)

Raphael Kubo da Costa via GitHub

• Re: [sensors] Should we check for "same origin" or "same origin-domain"? (#457) (Tuesday, 21 February)
• [sensors] Should we check for "same origin" or "same origin-domain"? (#457) (Tuesday, 21 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• Re: [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)
• [compute-pressure] Does the privacy test need a same origin-domain or a same origin check? (#187) (Tuesday, 21 February)

Tammy Walker via GitHub

• [contact-picker] Copyright (#62) (Sunday, 19 February)

Wei Wang via GitHub

• Re: [compute-pressure] Focus control in privacy test steps (#185) (Thursday, 16 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Tuesday, 14 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Thursday, 9 February)
• Re: [compute-pressure] Focus control in privacy test steps (#185) (Wednesday, 8 February)
• [compute-pressure] Focus control in privacy test steps (#185) (Wednesday, 8 February)

Last message date: Wednesday, 22 February 2023 05:09:35 UTC