Closed: [sensors] Add a section on how sensors are implemented
Re: [sensors] Add a section on how sensors are implemented
Closed: [sensors] No way to express an abstract constructor in WebIDL
Closed: [sensors] Clarify terminology
[battery] implementation testing report
[vibration] privacy consideration PING comments
- Re: [vibration] privacy consideration PING comments
RE: [battery] getBattery() test case feedback
Wake Lock implementation in Mozilla Firefox
Draft Minutes 2016-02-18 teleconference
DAP-ACTION-745: Request review of anssi update of vibration from wg and ping (pull request version)
Privacy call on Thursday 25 Feb at UTC 17 including Vibration API in agenda
[admin] Agenda - DAP Distributed Meeting 18 February 2016
[sensors] Discreet sensors must fire an event with their current state on instantiation
[vibration] Suggested changes for the Rec errata and Proposed Edited Rec
[sensors] constructor of "Abstract" Sensor
Re: [sensors] No way to express an abstract constructor in WebIDL
- Re: [sensors] No way to express an abstract constructor in WebIDL
- Re: [sensors] No way to express an abstract constructor in WebIDL
[sensors] sensorId : how are they named
- Re: [sensors] sensorId : how are they named
- Closed: [sensors] sensorId : how are they named
- Re: [sensors] sensorId : how are they named
- Closed: [sensors] sensorId : how are they named
Closed: [sensors] Identify the lower level primitives that do the actual sensor polling.
Re: [sensors] Identify the lower level primitives that do the actual sensor polling.
[admin] Draft Minutes from 2016-02-04 DAP teleconference
DAP-ACTION-744: Clarify battery test report , removing or explaining yellow at bottom of report
DAP-ACTION-743: Discuss with tobie how to generate report showing issues reported by others and how resolved
Re: [sensors] Provide a way of tying sensor requests to animation frames
[workmode] Forwarding GitHub Issue comments to the list considered harmful?
Closed: [sensors] Conformance requirements for concrete specs
Closed: [sensors] Define inantiation behavior in non top-level browsing contexts
[admin] Agenda - DAP Distributed Meeting 4 February 2016
Re: [vibration] Returning false if vibration hardware is not present?
- Re: [vibration] Returning false if vibration hardware is not present?
Re: [battery] Which events are to be fired when (un)plug in a charger?
- Re: [battery] Which events are to be fired when (un)plug in a charger?
- Re: [battery] Which events are to be fired when (un)plug in a charger?
- Re: [battery] Which events are to be fired when (un)plug in a charger?
Re: DAP-ISSUE-171: Returning false if vibration hardware is not present or using hasVibration? (prefer promises) [Vibration API]
Re: [sensors] Define behavior when visibilityState != "visible"
- Re: [sensors] Define behavior when visibilityState != "visible"
- Re: [sensors] Define behavior when visibilityState != "visible"
- Re: [sensors] Define behavior when visibilityState != "visible"
Re: [sensors] Conformance requirements for concrete specs
- Re: [sensors] Conformance requirements for concrete specs
- Re: [sensors] Conformance requirements for concrete specs
- Re: [sensors] Conformance requirements for concrete specs
- Re: [sensors] Conformance requirements for concrete specs
- Re: [sensors] Conformance requirements for concrete specs
- Re: [sensors] Conformance requirements for concrete specs