Thursday, 25 June 2015
- draft minutes 25 June 2015
- DAP-ACTION-737: Chat with geo chair and staff contact on future of device orientaiton
- DAP-ACTION-736: Send cfc for wd publication for ambient light and proximity once drafts available
- DAP-ACTION-735: Create editor drafts for ambient light and proximity indicating new approach toward generic sensor api, also drafts for publication to tr space
- DAP-ACTION-734: Contact mozilla and microsoft re interest in implementing html media capture vs shelving
- Re: [admin] Agenda - DAP Distributed Meeting 25 June 2015
- Re: [wake-lock] Wake Lock API Status request
- Re: [wake-lock] Wake Lock API Status request
Wednesday, 24 June 2015
- Re: [proximity/light] Way forward for Proximity/Light APIs
- Re: CfC to Shelve DAP Permissions API
- Re: [admin] Agenda - DAP Distributed Meeting 25 June 2015
- Re: CfC to Shelve DAP Permissions API
- RE: [Battery] Battery Status & Update request
Tuesday, 23 June 2015
- Fwd: DAP rechartering
- [admin] Agenda - DAP Distributed Meeting 25 June 2015
- Re: CfC to Shelve DAP Permissions API
- [proximity/light] Way forward for Proximity/Light APIs
- [wake-lock] Wake Lock API Status request
- [html-media-capture] HTML Media Capture Status and Update Request
- [Battery] Battery Status & Update request
Monday, 22 June 2015
Friday, 19 June 2015
Thursday, 18 June 2015
- Re: CfC to Shelve DAP Permissions API
- Re: CfC to Shelve DAP Permissions API
- CfC to Shelve DAP Permissions API
- DAP rechartering
- [sensors] Add a section on how sensors are implemented
- [sensors] Add a definitions section to the spec
Wednesday, 17 June 2015
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
Tuesday, 16 June 2015
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
- Re: [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
- [sensors] Address questions around exposing high-level, low-level, and uncalibrated sensors
Monday, 15 June 2015
Friday, 12 June 2015
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: TPAC breakout session for the Generic Sensor API? (was: TPAC 2015 Registration Now Open)
- TPAC breakout session for the Generic Sensor API? (was: TPAC 2015 Registration Now Open)
- Re: [sensors] Do we need a lightweight interface representing available sensors?
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
Thursday, 11 June 2015
- Re: [sensors] Is a Promise-returning, "oneshot" method useful?
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Is a Promise-returning, "oneshot" method useful?
- Re: [sensors] Is a Promise-returning, "oneshot" method useful?
- Re: [sensors] Is a Promise-returning, "oneshot" method useful?
- Re: [sensors] Is a Promise-returning, "oneshot" method useful?
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Is a Promise-returning, "oneshot" method useful?
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Updated proposal for Sensor API
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- [sensors] Is a Promise-returning, "oneshot" method useful?
- [sensors] Does `SensorObserver` need a stop() method?
- [sensors] Ability to lookup a cached SensorReading without polling the sensor
- Re: [sensors] Updated proposal for Sensor API
- Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors
- Re: [sensors] Handle sensor fusion
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Draft minutes from today's call 11 June 2015
- Re: [sensors] Handle sensor fusion
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- DAP-ACTION-733: Discuss generic sensor api and use of eventtarget in geolocation wg to summarize issues to dap
- Re: [sensors] Handle sensor fusion
- reminder - using WebEx for today's DAP call
- Re: [sensors] Provide a way of tying sensor requests to animation frames
- [sensors] Add a timeout property?
- [sensors] Add high resolution monotonic timestamps to SensorReadings
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Re: [sensors] fixing typos
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
Wednesday, 10 June 2015
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Re: [sensors] Use <dfn> tag for "read from the sensor"
- Re: [sensors] Handle sensor fusion
- Re: [sensors] Handle sensor fusion
- TPAC 2015 Registration Now Open
- [sensors] Handle sensor fusion
- Re: [admin] Agenda - DAP Distributed Meeting 11 June 2015
- Re: [admin] Agenda - DAP Distributed Meeting 11 June 2015
- Re: [admin] Agenda - DAP Distributed Meeting 11 June 2015
- Re: [admin] Agenda - DAP Distributed Meeting 11 June 2015
- Re: [admin] Agenda - DAP Distributed Meeting 11 June 2015
- Re: [sensors] Credit where credit is due.
- [sensors] Make APIs forward-compatible with ES modules
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
Tuesday, 9 June 2015
- Re: [sensors] Use double WebIDL type instead of float.
- Closed: [sensors] frequency is a float?
- Closed: [sensors] [TreatNonObjectAsNull] not required?
- Re: [sensors] Use <dfn> tag for "read from the sensor"
- Re: [sensors] getAll()?
- Re: [sensors] getAll()?
- Re: [sensors] getAll()?
- [admin] Agenda - DAP Distributed Meeting 11 June 2015
- Re: [sensors] [TreatNonObjectAsNull] not required?
- Re: [sensors] [TreatNonObjectAsNull] not required?
- [sensors] [TreatNonObjectAsNull] not required?
Monday, 8 June 2015
- Re: [sensors] getAll()?
- [sensors] frequency is a float?
- [sensors] getAll()?
- Re: [sensors] Do we need a lightweight interface representing available sensors?
- Initial ED of the Generic Sensor API
- Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
- Closed: [sensors] SensorIdentifier is bizarre
- Re: [sensors] Do we need a lightweight interface representing available sensors?
- Re: [sensors] Do we need a lightweight interface representing available sensors?
- Re: [sensors] Do we need a lightweight interface representing available sensors?
- Re: [sensors] SensorIdentifier is bizarre
- Re: [sensors] SensorIdentifier is bizarre
- [sensors] SensorIdentifier is bizarre
- Re: [sensors] Do we need a lightweight interface representing available sensors?
- Re: [sensors] Do we need a lightweight interface representing available sensors?
- [sensors] Do we need a lightweight interface representing available sensors?
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
Sunday, 7 June 2015
Saturday, 6 June 2015
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- Re: [sensors] Fix mixed-content problem with URL to respec
- Re: [sensors] Identify the lower level primitives that do the actual sensor polling.
Friday, 5 June 2015
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- Re: [sensors] Add a threshold option
- Re: [sensors] Identify the lower level primitives that do the actual sensor polling.
- Re: [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- [sensors] When there are multiple sensors of a given type, how do we identify which one to instantiate?
- [sensors] Add a threshold option
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- [sensors] Identify the lower level primitives that do the actual sensor polling.
Thursday, 4 June 2015
Wednesday, 3 June 2015
- Re: [sensors] What if requested polling frequency is > time it takes to read data out of the sensor?
- Re: [sensors] What if requested polling frequency is > time it takes to read data out of the sensor?
- [sensors] What if requested polling frequency is > time it takes to read data out of the sensor?
- Re: [sensors] "wakeup" parameter
- Re: [sensors] "wakeup" parameter
- Re: [sensors] "wakeup" parameter
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
Tuesday, 2 June 2015
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget
- Re: [sensors] Dependency on [DOM] due to inheriting from EventTarget