public-device-apis@w3.org from March 2016 by author

Andrey Logvinov

[wake-lock] Wake Lock API Security & Privacy Questionnaire self-review (Wednesday, 9 March)
Wake Lock API Security & Privacy Questionnaire self-review (Wednesday, 9 March)
Re: [wake-lock] Wake Lock API status update (Wednesday, 2 March)

Anne van Kesteren via GitHub

Re: [sensors] Add solution for one-shot readings (Thursday, 10 March)
Re: [sensors] Add solution for one-shot readings (Monday, 7 March)

Anssi Kostiainen via GitHub

Re: [ambient-light] Add bikeshed index file. (Wednesday, 23 March)
Re: [ambient-light] Add bikeshed index file. (Wednesday, 23 March)
Re: [sensors] Typos. (Tuesday, 22 March)
Re: [sensors] Handling fatal vs. transient errors (Friday, 18 March)
Re: [sensors] Clarify terminology (Monday, 14 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)

Chaals McCathie Nevile

Re: Exiting CR Re: [wake-lock] Wake Lock API status update (Tuesday, 15 March)
Re: [wake-lock] Wake Lock API status update (Monday, 14 March)
Exiting CR Re: [wake-lock] Wake Lock API status update (Wednesday, 2 March)

Device APIs Working Group Issue Tracker

DAP-ACTION-753: Update Web IDL Level 1 reference to reference new WebIDL CR publication in editors draft and PR draft (Monday, 14 March)
DAP-ACTION-752: to review wake lock with respect to privacy and security https://w3ctag.github.io/security-questionnaire/ (Thursday, 3 March)
DAP-ACTION-751: Prepare new vibration editors draft including errata and security and privacy consideration material from lukasz and others (Thursday, 3 March)
DAP-ACTION-750: Create draft security and privacy considerations section for vibration api (Thursday, 3 March)
DAP-ACTION-749: Send transition request (Thursday, 3 March)
DAP-ACTION-748: Put tentative date of 3 may 2016 in battery pr draft (Thursday, 3 March)
DAP-ACTION-747: Create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk (Thursday, 3 March)
DAP-ACTION-746: Update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html (Thursday, 3 March)
ISSUE-174: Anssik to put tentative date of 3 may 2016 in battery pr draft (Thursday, 3 March)
ISSUE-173: Anssik to create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk (Thursday, 3 March)
ISSUE-172: Anssik update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html (Thursday, 3 March)

Domenic Denicola via GitHub

Re: [sensors] Add solution for one-shot readings (Monday, 7 March)

Dominique Hazael-Massieux

[admin] Reminder: no DAP call today (Thursday, 31 March)
New charter approved; rejoin the group (Thursday, 31 March)
New WD of Ambient Light API (Tuesday, 29 March)
Battery API is a W3C Proposed Recommendation (Tuesday, 29 March)
New generic sensor API WD out (Thursday, 24 March)
[minutes] DAP Distributed Meeting 17 March 2016 (Thursday, 17 March)
Summer Time! (was: [admin] Agenda - DAP Distributed Meeting 17 March 2016) (Wednesday, 16 March)
Re: [wake-lock] Wake Lock API Security & Privacy Questionnaire self-review (Wednesday, 9 March)
[wake-lock] Wide review of Wake Lock API (Wednesday, 2 March)

Dominique Hazael-Massieux via GitHub

Re: [sensors] Setup echidna for continuous deployment (Wednesday, 30 March)
Re: [sensors] Setup echidna for continuous deployment (Wednesday, 30 March)
Re: [ambient-light] Add bikeshed index file. (Thursday, 24 March)
Re: [sensors] Is there a need for a oncalibrationneeded event (Thursday, 17 March)
[sensors] Prepare licensing change in spec (Wednesday, 16 March)

Frederick Hirsch

Re: New generic sensor API WD out (Thursday, 24 March)
[admin] Agenda - DAP Distributed Meeting 17 March 2016 (Monday, 14 March)
Call for Consensus to transition Battery API to Proposed Recommendation (PR) completed successfully (Monday, 14 March)
Re: Wake Lock API Security & Privacy Questionnaire self-review (Monday, 14 March)
Re: Wake Lock API Security & Privacy Questionnaire self-review (Monday, 14 March)
CfC: Call for Consensus to transition Battery API to Proposed Recommendation (PR) : deadline 10 March (Friday, 4 March)
Draft minutes 3 March 2016 and Action summary (Thursday, 3 March)
[admin] Agenda - DAP Distributed Meeting 3 March 2016 (Tuesday, 1 March)
[battery] Next steps to PR (was: implementation testing report) (Tuesday, 1 March)

Greg Norcie

Re: Privacy report on sensors, for generic sensors API. (Tuesday, 29 March)

Kostiainen, Anssi

Re: Battery API is a W3C Proposed Recommendation (Tuesday, 29 March)
Re: New generic sensor API WD out (Thursday, 24 March)
Re: Call for Consensus to transition Battery API to Proposed Recommendation (PR) completed successfully (Thursday, 17 March)

Lukasz Olejnik (W3C)

Re: Privacy report on sensors, for generic sensors API. (Tuesday, 29 March)
Privacy report on sensors, for generic sensors API. (Tuesday, 29 March)
Re: DAP-ACTION-750: Create draft security and privacy considerations section for vibration api (Sunday, 6 March)

Marcos Caceres

Re: [wake-lock] Wake Lock API status update (Tuesday, 15 March)
Re: Exiting CR Re: [wake-lock] Wake Lock API status update (Monday, 14 March)
Re: [wake-lock] Wake Lock API status update (Monday, 14 March)

Marcos Caceres via GitHub

Re: [sensors] Adding a sensor.activated attribute (Monday, 21 March)
Re: [sensors] Adding a sensor.activated attribute (Monday, 21 March)
Re: [sensors] Add solution for one-shot readings (Wednesday, 16 March)

Rick Waldron via GitHub

Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)

Robin Berjon via GitHub

Re: [sensors] Add solution for one-shot readings (Monday, 7 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)

timeless

Re: [wake-lock] Wake Lock API status update (Wednesday, 2 March)

Tobie Langel via GitHub

Re: [ambient-light] Add bikeshed index file. (Wednesday, 23 March)
Re: [ambient-light] Add bikeshed index file. (Wednesday, 23 March)
Closed: [sensors] Spec should allow user agents to reduce or disable sensor read for power saving purposes (Tuesday, 22 March)
Re: [sensors] Spec should allow user agents to reduce or disable sensor read for power saving purposes (Tuesday, 22 March)
Closed: [sensors] Define behavior when visibilityState != "visible" (Tuesday, 22 March)
Re: [sensors] Define behavior when visibilityState != "visible" (Tuesday, 22 March)
Closed: [sensors] Discreet sensors must fire an event with their current state on instantiation (Tuesday, 22 March)
Re: [sensors] Discreet sensors must fire an event with their current state on instantiation (Tuesday, 22 March)
Closed: [sensors] Discrete vs continuous reporting modes (Tuesday, 22 March)
Re: [sensors] Discrete vs continuous reporting modes (Tuesday, 22 March)
Closed: [sensors] What if requested polling frequency is > time it takes to read data out of the sensor? (Tuesday, 22 March)
Re: [sensors] What if requested polling frequency is > time it takes to read data out of the sensor? (Tuesday, 22 March)
Closed: [sensors] Allow for async permission request when first accessing sensor data (Tuesday, 22 March)
Re: [sensors] Define behavior when multiple instances of a sensor set different settings (Tuesday, 22 March)
Closed: [sensors] Define behavior when multiple instances of a sensor set different settings (Tuesday, 22 March)
Closed: [sensors] Clarify terminology (Tuesday, 22 March)
Re: [sensors] Clarify terminology (Tuesday, 22 March)
Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors (Tuesday, 22 March)
Closed: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors (Tuesday, 22 March)
Re: [sensors] Should sensors be singleton? (Tuesday, 22 March)
Closed: [sensors] Should sensors be singleton? (Tuesday, 22 March)
Closed: [sensors] Handling fatal vs. transient errors (Tuesday, 22 March)
Re: [sensors] Allow for async permission request when first accessing sensor data (Tuesday, 22 March)
Re: [sensors] Adding a sensor.activated attribute (Monday, 21 March)
[sensors] Adding a sensor.activated attribute (Sunday, 20 March)
[sensors] start() to return a cancellable promise that resolves on first reading (Sunday, 20 March)
[sensors] Handling fatal vs. transient errors (Friday, 18 March)
Re: [sensors] Is there a need for a oncalibrationneeded event (Thursday, 17 March)
[sensors] Is there a need for a oncalibrationneeded event (Thursday, 17 March)
Re: [sensors] Prepare licensing change in spec (Wednesday, 16 March)
Re: [sensors] Add solution for one-shot readings (Thursday, 10 March)
Re: [sensors] Add solution for one-shot readings (Thursday, 10 March)
Re: [sensors] Add solution for one-shot readings (Thursday, 10 March)
Re: [sensors] Add solution for one-shot readings (Thursday, 10 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
Re: [sensors] Add solution for one-shot readings (Sunday, 6 March)
[sensors] Add solution for cached value readings (Sunday, 6 March)
[sensors] Add solution for one-shot readings (Sunday, 6 March)

Zhang, Zhiqiang

RE: [battery] implementation testing report (Wednesday, 2 March)

Zoltan Kis via GitHub

Re: [sensors] Adding a sensor.activated attribute (Monday, 21 March)

Last message date: Thursday, 31 March 2016 10:59:33 UTC