- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 30 May 2017 17:00:15 +0000
- To: public-device-apis@w3.org
- Message-Id: <E1dFkVD-00037r-W6@uranus.w3.org>
Issues ------ * w3c/sensors (+11/-7/💬129) 11 issues created: - Should a "suspended" state be added (by tobie) https://github.com/w3c/sensors/issues/223 - Missing browsing-context focus/unfocus hooks in HTML spec. (by tobie) https://github.com/w3c/sensors/issues/222 - Investigate adding dedicated task sources (by tobie) https://github.com/w3c/sensors/issues/221 - Should update sensor reading task be in sync with latest reading? (by alexshalamov) https://github.com/w3c/sensors/issues/220 - Define parameters for events (by alexshalamov) https://github.com/w3c/sensors/issues/219 - Define tasks for state changes (by alexshalamov) https://github.com/w3c/sensors/issues/218 - Define algorithm for suspending / resuming activated sensor objects (by alexshalamov) https://github.com/w3c/sensors/issues/217 - Clarify relationship between Sensor object and task source (by alexshalamov) https://github.com/w3c/sensors/issues/216 - Use simple event dispatch mechanism instead of task source (queued) (by alexshalamov) https://github.com/w3c/sensors/issues/215 - Sensors unable to provide their state when instantiated (by tobie) https://github.com/w3c/sensors/issues/214 - Clarify sensor task source scope (by tobie) https://github.com/w3c/sensors/issues/212 15 issues received 129 new comments: - #209 Use ''sampling frequency" instead of "polling frequency" (28 by tobie, alexshalamov, pozdnyakov) https://github.com/w3c/sensors/issues/209 - #215 Use simple event dispatch mechanism instead of task source (queued) (28 by tobie, pozdnyakov, anssiko, alexshalamov) https://github.com/w3c/sensors/issues/215 - #152 Call 'onchange' on a Senor instance considering its own frequency hint (26 by tobie, pozdnyakov, anssiko, alexshalamov) https://github.com/w3c/sensors/issues/152 - #198 Define processing model (22 by tobie, pozdnyakov, anssiko, alexshalamov) https://github.com/w3c/sensors/issues/198 - #220 Should update sensor reading task be in sync with latest reading? (5 by tobie, alexshalamov) https://github.com/w3c/sensors/issues/220 - #217 Define algorithm for suspending / resuming activated sensor objects (4 by tobie, alexshalamov) https://github.com/w3c/sensors/issues/217 - #216 Clarify relationship between Sensor object and task source (3 by tobie, alexshalamov) https://github.com/w3c/sensors/issues/216 - #212 Clarify sensor task source scope (3 by tobie, alexshalamov) https://github.com/w3c/sensors/issues/212 - #196 Take into account user gestures as an input for security policy enforcement (2 by tobie, ojanvafai) https://github.com/w3c/sensors/issues/196 - #205 Agree on event names (2 by anssiko, pozdnyakov) https://github.com/w3c/sensors/issues/205 - #221 Investigate adding dedicated task sources (2 by tobie, anssiko) https://github.com/w3c/sensors/issues/221 - #188 [meta] Publish a new Working Draft (1 by anssiko) https://github.com/w3c/sensors/issues/188 - #202 The Handle Errors abstract operation must deactivate the activated Sensor object (1 by tobie) https://github.com/w3c/sensors/issues/202 - #218 Define tasks for state changes (1 by tobie) https://github.com/w3c/sensors/issues/218 - #219 Define parameters for events (1 by tobie) https://github.com/w3c/sensors/issues/219 7 issues closed: - The Handle Errors abstract operation must deactivate the activated Sensor object https://github.com/w3c/sensors/issues/202 - Clarify sensor task source scope https://github.com/w3c/sensors/issues/212 - Define algorithm for suspending / resuming activated sensor objects https://github.com/w3c/sensors/issues/217 - Missing browsing-context focus/unfocus hooks in HTML spec. https://github.com/w3c/sensors/issues/222 - Avoid PIN skimming attacks https://github.com/w3c/sensors/issues/189 - Define parameters for events https://github.com/w3c/sensors/issues/219 - [meta] Publish a new Working Draft https://github.com/w3c/sensors/issues/188 * w3c/ambient-light (+0/-0/💬2) 1 issues received 2 new comments: - #13 Security and Privacy considerations for ALS (2 by lknik, alexshalamov) https://github.com/w3c/ambient-light/issues/13 Pull requests ------------- * w3c/sensors (+3/-2/💬22) 3 pull requests submitted: - Use the has focus steps algorithm. (by tobie) https://github.com/w3c/sensors/pull/225 - Use focus chain. (by tobie) https://github.com/w3c/sensors/pull/224 - Add mitigation strategy for skimming attacks when focus is lost. (by tobie) https://github.com/w3c/sensors/pull/213 5 pull requests received 22 new comments: - #213 Add mitigation strategy for skimming attacks when focus is lost. (13 by tobie, pozdnyakov, alexshalamov) https://github.com/w3c/sensors/pull/213 - #197 Rewrite Abstract Operations (4 by tobie, anssiko, alexshalamov) https://github.com/w3c/sensors/pull/197 - #225 Use the has focus steps algorithm. (2 by tobie, kenchris) https://github.com/w3c/sensors/pull/225 - #210 Sensor objects have their own reading copies (2 by tobie, pozdnyakov) https://github.com/w3c/sensors/pull/210 - #224 Use focus chain. (1 by tobie) https://github.com/w3c/sensors/pull/224 2 pull requests merged: - Use the has focus steps algorithm. https://github.com/w3c/sensors/pull/225 - Add mitigation strategy for skimming attacks when focus is lost. https://github.com/w3c/sensors/pull/213 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, 30 May 2017 17:00:23 UTC