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

Alexander Shalamov via GitHub

Re: [sensors] Don't allocate response objects to avoid triggering GC (Friday, 16 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Friday, 16 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Friday, 9 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)

Andrey Logvinov via GitHub

Closed: [wake-lock] Several defined terms are way too generic (Tuesday, 20 December)
Re: [wake-lock] Several defined terms are way too generic (Tuesday, 20 December)
Re: [wake-lock] Current API not friendly to components (Tuesday, 20 December)
Closed: [wake-lock] Current API not friendly to components (Tuesday, 20 December)
Closed: [wake-lock] System lock should be specified (Tuesday, 20 December)
Re: [wake-lock] System lock should be specified (Tuesday, 20 December)
Closed: [wake-lock] Plans for v2 (Tuesday, 20 December)
[wake-lock] Review the Privacy & Security section (Tuesday, 20 December)
Re: [wake-lock] Spec update (Tuesday, 20 December)
Re: [wake-lock] Spec update (Thursday, 15 December)

legion80 via GitHub

Re: [html-media-capture] VideoFacingModeEnum as the capture attribute's value (Thursday, 22 December)

Mark Foltz via GitHub

[magnetometer] Local coordinates could use further detail/examples (Monday, 26 December)
[magnetometer] Shouldn't need Web Service to compute declination (Monday, 26 December)
[sensors] SensorReading.timeStamp could be clarified (Monday, 26 December)
[sensors] Need API to report platform accuracy changes (Monday, 26 December)
[ambient-light] Auto reporting mode is not defined (Monday, 26 December)

Mikhail Pozdnyakov via GitHub

Re: [sensors] Call 'onchange' only when data changes and considering frequency hint (Friday, 16 December)
Re: [sensors] SensorErrorEvent IDL doesn't match Blink (Thursday, 15 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)

moka via GitHub

Re: [sensors] Don't allocate response objects to avoid triggering GC (Monday, 19 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Friday, 16 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Friday, 9 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)

Philip Jägenstedt via GitHub

Re: [sensors] Call 'onchange' only when data changes and considering frequency hint (Monday, 19 December)
Re: [sensors] Call 'onchange' only when data changes and considering frequency hint (Saturday, 17 December)
Re: [sensors] Call 'onchange' only when data changes and considering frequency hint (Friday, 16 December)
Re: [sensors] Call 'onchange' only when data changes and considering frequency hint (Friday, 16 December)

Rick Waldron via GitHub

Re: [sensors] Don't allocate response objects to avoid triggering GC (Monday, 19 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)

Tobie Langel via GitHub

Re: [sensors] Call 'onchange' only when data changes and considering frequency hint (Sunday, 18 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Sunday, 18 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Sunday, 18 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Sunday, 18 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Sunday, 18 December)
Re: [sensors] Call 'onchange' only when data changes and considering frequency hint (Friday, 16 December)
Re: [sensors] Add abstract operation for constructing a SensorReading (Thursday, 15 December)
Closed: [sensors] Add abstract operation for constructing a SensorReading (Thursday, 15 December)
Re: [sensors] SensorReadings must be immutable. (Thursday, 15 December)
Closed: [sensors] SensorReadings must be immutable. (Thursday, 15 December)
Closed: [sensors] Should SensorReading be a dictionary? (Thursday, 15 December)
Re: [sensors] Should SensorReading be a dictionary? (Thursday, 15 December)
Closed: [sensors] SensorErrorEvent IDL doesn't match Blink (Monday, 12 December)
Re: [sensors] SensorErrorEvent IDL doesn't match Blink (Monday, 12 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Friday, 9 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Wednesday, 7 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)
Re: [sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)
[sensors] Don't allocate response objects to avoid triggering GC (Tuesday, 6 December)

Last message date: Monday, 26 December 2016 19:39:22 UTC