- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 06 Jun 2017 17:00:11 +0000
- To: public-device-apis@w3.org
- Message-Id: <E1dIHpz-0001Uw-Pl@uranus.w3.org>
Issues
------
* w3c/sensors (+2/-4/💬30)
2 issues created:
- Define algorithm for suspending / resuming activated sensor objects (by alexshalamov)
https://github.com/w3c/sensors/issues/227
- Mark mitigation strategy section as informative and avoid RFC2119 language in it. (by tobie)
https://github.com/w3c/sensors/issues/226
7 issues received 30 new comments:
- #209 Should the API allow setting both samplingFrequency and reportingFrequency? (17 by tobie, pozdnyakov, rwaldron, anssiko, alexshalamov)
https://github.com/w3c/sensors/issues/209
- #218 Define tasks for state changes (4 by tobie, alexshalamov)
https://github.com/w3c/sensors/issues/218
- #227 Define algorithm for suspending / resuming activated sensor objects (3 by tobie, alexshalamov)
https://github.com/w3c/sensors/issues/227
- #216 Clarify relationship between Sensor object and task source (3 by tobie, alexshalamov)
https://github.com/w3c/sensors/issues/216
- #198 Define processing model (1 by pozdnyakov)
https://github.com/w3c/sensors/issues/198
- #220 Should update sensor reading task be in sync with latest reading? (1 by tobie)
https://github.com/w3c/sensors/issues/220
- #222 Missing browsing-context focus/unfocus hooks in HTML spec. (1 by tobie)
https://github.com/w3c/sensors/issues/222
4 issues closed:
- Reading attributes at different sensor states https://github.com/w3c/sensors/issues/168
- Should update sensor reading task be in sync with latest reading? https://github.com/w3c/sensors/issues/220
- Clarify relationship between Sensor object and task source https://github.com/w3c/sensors/issues/216
- Mark mitigation strategy section as informative and avoid RFC2119 language in it. https://github.com/w3c/sensors/issues/226
* w3c/accelerometer (+1/-0/💬0)
1 issues created:
- Add use cases to spec (by owencm)
https://github.com/w3c/accelerometer/issues/18
* w3c/gyroscope (+1/-1/💬0)
1 issues created:
- Add link to use cases in spec (by owencm)
https://github.com/w3c/gyroscope/issues/13
1 issues closed:
- Add link to use cases in spec https://github.com/w3c/gyroscope/issues/13
* w3c/magnetometer (+1/-2/💬2)
1 issues created:
- Link to use cases in the spec (by owencm)
https://github.com/w3c/magnetometer/issues/26
2 issues received 2 new comments:
- #26 Link to use cases in the spec (1 by anssiko)
https://github.com/w3c/magnetometer/issues/26
- #5 Permission (1 by anssiko)
https://github.com/w3c/magnetometer/issues/5
2 issues closed:
- Permission https://github.com/w3c/magnetometer/issues/5
- Link to use cases in the spec https://github.com/w3c/magnetometer/issues/26
* w3c/battery (+0/-0/💬3)
2 issues received 3 new comments:
- #12 [meta] Publish a revised Candidate Recommendation (2 by Honry, anssiko)
https://github.com/w3c/battery/issues/12
- #10 Allow use from within secure context and top-level browsing context only (1 by anssiko)
https://github.com/w3c/battery/issues/10
* w3c/wake-lock (+3/-0/💬0)
3 issues created:
- Specify that platform-specific inactivity timer should be reset after the lock is released (by andrey-logvinov)
https://github.com/w3c/wake-lock/issues/101
- Restrict Wake Lock to secure context (by andrey-logvinov)
https://github.com/w3c/wake-lock/issues/100
- Disable Wake Lock in sandboxed frames (by andrey-logvinov)
https://github.com/w3c/wake-lock/issues/99
Pull requests
-------------
* w3c/sensors (+5/-3/💬14)
5 pull requests submitted:
- [DO NOT MERGE] Add preliminary interactive diagram. (by tobie)
https://github.com/w3c/sensors/pull/232
- Update Sensor.timestamp description (by pozdnyakov)
https://github.com/w3c/sensors/pull/231
- Add Get value from latest reading abstract op. (by tobie)
https://github.com/w3c/sensors/pull/230
- Queue tasks for [[state]] changes. (by tobie)
https://github.com/w3c/sensors/pull/229
- Make mitigation strategy section informative. (by tobie)
https://github.com/w3c/sensors/pull/228
4 pull requests received 14 new comments:
- #213 Add mitigation strategy for skimming attacks when focus is lost. (10 by tobie, anssiko, alexshalamov)
https://github.com/w3c/sensors/pull/213
- #210 Sensor objects fire 'change' event considering their own frequency hint (2 by tobie, pozdnyakov)
https://github.com/w3c/sensors/pull/210
- #229 Queue tasks for [[state]] changes. (1 by kenchris)
https://github.com/w3c/sensors/pull/229
- #231 Update Sensor.timestamp description (1 by tobie)
https://github.com/w3c/sensors/pull/231
3 pull requests merged:
- Update Sensor.timestamp description
https://github.com/w3c/sensors/pull/231
- Add Get value from latest reading abstract op.
https://github.com/w3c/sensors/pull/230
- Make mitigation strategy section informative.
https://github.com/w3c/sensors/pull/228
* w3c/gyroscope (+1/-1/💬0)
1 pull requests submitted:
- Add link to use cases (by pozdnyakov)
https://github.com/w3c/gyroscope/pull/14
1 pull requests merged:
- Add link to use cases
https://github.com/w3c/gyroscope/pull/14
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/sensors
* https://github.com/w3c/ambient-light
* https://github.com/w3c/accelerometer
* https://github.com/w3c/proximity
* https://github.com/w3c/gyroscope
* https://github.com/w3c/magnetometer
* https://github.com/w3c/orientation-sensor
* https://github.com/w3c/motion-sensors
* https://github.com/w3c/battery
* https://github.com/w3c/wake-lock
* https://github.com/w3c/html-media-capture
* https://github.com/w3c/vibration
Received on Tuesday, 6 June 2017 17:00:18 UTC