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

Andrey Logvinov

Wake Lock implementation in Mozilla Firefox (Friday, 19 February)

Anssi Kostiainen via GitHub

Re: [sensors] No way to express an abstract constructor in WebIDL (Friday, 5 February)
Re: [sensors] Define behavior when visibilityState != "visible" (Wednesday, 3 February)
Re: [sensors] Define behavior when visibilityState != "visible" (Tuesday, 2 February)
Re: [sensors] Conformance requirements for concrete specs (Monday, 1 February)
Re: [sensors] Conformance requirements for concrete specs (Monday, 1 February)

Chaals McCathie Nevile

Re: [vibration] privacy consideration PING comments (Saturday, 27 February)
Re: Privacy call on Thursday 25 Feb at UTC 17 including Vibration API in agenda (Thursday, 18 February)
Re: [vibration] Suggested changes for the Rec errata and Proposed Edited Rec (Friday, 12 February)
Re: [vibration] Returning false if vibration hardware is not present? (Wednesday, 3 February)
Re: [vibration] Returning false if vibration hardware is not present? (Wednesday, 3 February)

chaals via GitHub

Re: [sensors] Conformance requirements for concrete specs (Monday, 1 February)

Christine Runnegar

Re: Privacy call on Thursday 25 Feb at UTC 17 including Vibration API in agenda (Thursday, 25 February)

David (Standards) Singer

Re: [vibration] privacy consideration PING comments (Monday, 29 February)

David Singer

Re: [vibration] privacy consideration PING comments (Monday, 29 February)
Re: [vibration] privacy consideration PING comments (Monday, 29 February)

Device APIs Working Group Issue Tracker

DAP-ACTION-745: Request review of anssi update of vibration from wg and ping (pull request version) (Thursday, 18 February)
DAP-ACTION-744: Clarify battery test report , removing or explaining yellow at bottom of report (Thursday, 4 February)
DAP-ACTION-743: Discuss with tobie how to generate report showing issues reported by others and how resolved (Thursday, 4 February)

Dominique Hazael-Massieux

Re: [vibration] Returning false if vibration hardware is not present? (Wednesday, 3 February)

Frederick Hirsch

Re: [battery] implementation testing report (Friday, 26 February)
[vibration] privacy consideration PING comments (Friday, 26 February)
Draft Minutes 2016-02-18 teleconference (Thursday, 18 February)
Privacy call on Thursday 25 Feb at UTC 17 including Vibration API in agenda (Thursday, 18 February)
[admin] Agenda - DAP Distributed Meeting 18 February 2016 (Monday, 15 February)
Re: [vibration] Suggested changes for the Rec errata and Proposed Edited Rec (Monday, 15 February)
[admin] Draft Minutes from 2016-02-04 DAP teleconference (Thursday, 4 February)
Re: [sensors] Define behavior when visibilityState != "visible" (Wednesday, 3 February)
Re: [vibration] Returning false if vibration hardware is not present? (Wednesday, 3 February)
Re: [vibration] Returning false if vibration hardware is not present? (Wednesday, 3 February)
[admin] Agenda - DAP Distributed Meeting 4 February 2016 (Wednesday, 3 February)
Re: DAP-ISSUE-171: Returning false if vibration hardware is not present or using hasVibration? (prefer promises) [Vibration API] (Wednesday, 3 February)
Re: [sensors] Conformance requirements for concrete specs (Wednesday, 3 February)
Re: [vibration] Returning false if vibration hardware is not present? (Wednesday, 3 February)

Joseph Lorenzo Hall

Re: [vibration] privacy consideration PING comments (Monday, 29 February)

Kostiainen, Anssi

Re: [battery] implementation testing report (Friday, 26 February)
Re: [battery] getBattery() test case feedback (Thursday, 25 February)
Re: [vibration] Suggested changes for the Rec errata and Proposed Edited Rec (Friday, 12 February)
Re: [battery] Which events are to be fired when (un)plug in a charger? (Wednesday, 10 February)
[vibration] Suggested changes for the Rec errata and Proposed Edited Rec (Tuesday, 9 February)
Re: [workmode] Forwarding GitHub Issue comments to the list considered harmful? (Thursday, 4 February)
Re: [vibration] Returning false if vibration hardware is not present? (Wednesday, 3 February)
Re: [battery] Which events are to be fired when (un)plug in a charger? (Tuesday, 2 February)
Re: [battery] Which events are to be fired when (un)plug in a charger? (Tuesday, 2 February)
Re: DAP-ISSUE-171: Returning false if vibration hardware is not present or using hasVibration? (prefer promises) [Vibration API] (Tuesday, 2 February)

Lukasz Olejnik (W3C)

Re: [vibration] privacy consideration PING comments (Monday, 29 February)
Re: [vibration] privacy consideration PING comments (Monday, 29 February)
Re: [vibration] privacy consideration PING comments (Monday, 29 February)
Re: [vibration] privacy consideration PING comments (Monday, 29 February)
Re: [vibration] privacy consideration PING comments (Saturday, 27 February)
Re: [vibration] privacy consideration PING comments (Saturday, 27 February)
Re: [vibration] Suggested changes for the Rec errata and Proposed Edited Rec (Friday, 12 February)
Re: DAP-ISSUE-171: Returning false if vibration hardware is not present or using hasVibration? (prefer promises) [Vibration API] (Wednesday, 3 February)
Re: DAP-ISSUE-171: Returning false if vibration hardware is not present or using hasVibration? (prefer promises) [Vibration API] (Tuesday, 2 February)
Re: [battery] Which events are to be fired when (un)plug in a charger? (Tuesday, 2 February)

Marcos Caceres via GitHub

Re: [sensors] Define behavior when visibilityState != "visible" (Wednesday, 3 February)
Re: [sensors] Conformance requirements for concrete specs (Monday, 1 February)

Rick Waldron via GitHub

Re: [sensors] Identify the lower level primitives that do the actual sensor polling. (Friday, 5 February)

Rijubrata Bhaumik via GitHub

[sensors] constructor of "Abstract" Sensor (Friday, 5 February)
[sensors] sensorId : how are they named (Friday, 5 February)

Tobie Langel

Re: [admin] Agenda - DAP Distributed Meeting 18 February 2016 (Thursday, 18 February)
Re: [battery] Which events are to be fired when (un)plug in a charger? (Wednesday, 10 February)
[workmode] Forwarding GitHub Issue comments to the list considered harmful? (Thursday, 4 February)

Tobie Langel via GitHub

Closed: [sensors] Add a section on how sensors are implemented (Friday, 26 February)
Re: [sensors] Add a section on how sensors are implemented (Friday, 26 February)
Closed: [sensors] No way to express an abstract constructor in WebIDL (Friday, 26 February)
Closed: [sensors] Clarify terminology (Friday, 26 February)
Closed: [sensors] sensorId : how are they named (Tuesday, 16 February)
[sensors] Discreet sensors must fire an event with their current state on instantiation (Wednesday, 10 February)
Re: [sensors] sensorId : how are they named (Friday, 5 February)
Closed: [sensors] sensorId : how are they named (Friday, 5 February)
Re: [sensors] No way to express an abstract constructor in WebIDL (Friday, 5 February)
Closed: [sensors] constructor of "Abstract" Sensor (Friday, 5 February)
Re: [sensors] constructor of "Abstract" Sensor (Friday, 5 February)
Re: [sensors] sensorId : how are they named (Friday, 5 February)
Re: [sensors] No way to express an abstract constructor in WebIDL (Friday, 5 February)
Closed: [sensors] Identify the lower level primitives that do the actual sensor polling. (Friday, 5 February)
Re: [sensors] Identify the lower level primitives that do the actual sensor polling. (Friday, 5 February)
Re: [sensors] Provide a way of tying sensor requests to animation frames (Thursday, 4 February)
Closed: [sensors] Conformance requirements for concrete specs (Thursday, 4 February)
Closed: [sensors] Define inantiation behavior in non top-level browsing contexts (Wednesday, 3 February)
Re: [sensors] Define behavior when visibilityState != "visible" (Wednesday, 3 February)
Re: [sensors] Conformance requirements for concrete specs (Monday, 1 February)
Re: [sensors] Conformance requirements for concrete specs (Monday, 1 February)
Re: [sensors] Conformance requirements for concrete specs (Monday, 1 February)

Zhang, Zhiqiang

[battery] implementation testing report (Friday, 26 February)
RE: [battery] getBattery() test case feedback (Thursday, 25 February)
RE: [battery] getBattery() test case feedback (Wednesday, 24 February)
RE: [battery] Which events are to be fired when (un)plug in a charger? (Wednesday, 17 February)
RE: [battery] Which events are to be fired when (un)plug in a charger? (Tuesday, 16 February)
RE: [battery] Which events are to be fired when (un)plug in a charger? (Tuesday, 16 February)

Last message date: Monday, 29 February 2016 22:04:19 UTC