Weekly github digest (Devices and Sensors WG specifications)

Issues
------
* w3c/proximity (+0/-0/💬2)
  1 issues received 2 new comments:
  - #44 Behavior of `distance` attribute when sensor cannot provide distance measurements? (2 by andycarle, anssiko)
    https://github.com/w3c/proximity/issues/44 

* w3c/geolocation-api (+0/-5/💬19)
  6 issues received 19 new comments:
  - #57 Security review: General observations (1 by marcoscaceres)
    https://github.com/w3c/geolocation-api/issues/57 [security-tracker] 
  - #56 Section 6: Non-normative but containing implementation requirements? (3 by magnus-git, marcoscaceres, samuelweiler)
    https://github.com/w3c/geolocation-api/issues/56 [security-needs-resolution] 
  - #54 Section 3: Why only "SHOULD" for protection of privacy? (5 by marcoscaceres, reillyeon)
    https://github.com/w3c/geolocation-api/issues/54 [privacy-needs-resolution] 
  - #50 Change text for description of GeolocationPositionError.message attribute (1 by marcoscaceres)
    https://github.com/w3c/geolocation-api/issues/50 [i18n-needs-resolution] 
  - #47 Explicitly limit permission lifetimes (5 by marcoscaceres, pes10k, reillyeon)
    https://github.com/w3c/geolocation-api/issues/47 [privacy-needs-resolution] [privacy-tracker] 
  - #42 Republish REC?  (4 by anssiko, marcoscaceres)
    https://github.com/w3c/geolocation-api/issues/42 

  5 issues closed:
  - Section 6: Non-normative but containing implementation requirements? https://github.com/w3c/geolocation-api/issues/56 [security-needs-resolution] 
  - Security review: General observations https://github.com/w3c/geolocation-api/issues/57 [security-tracker] 
  - Explicitly limit permission lifetimes https://github.com/w3c/geolocation-api/issues/47 [privacy-tracker] 
  - errorCallback parameter to getPosition() and watchPosition() is nullable in all major browser engines https://github.com/w3c/geolocation-api/issues/61 
  - Change text for description of GeolocationPositionError.message attribute https://github.com/w3c/geolocation-api/issues/50 [i18n-needs-resolution] 

* w3c/screen-wake-lock (+0/-1/💬1)
  1 issues received 1 new comments:
  - #300 Auto-releasing wake lock depending on the user presence (1 by marcoscaceres)
    https://github.com/w3c/screen-wake-lock/issues/300 

  1 issues closed:
  - "Release a wake lock": should we queue a task to fire the "release" event? https://github.com/w3c/screen-wake-lock/issues/293 



Pull requests
-------------
* w3c/geolocation-api (+7/-3/💬12)
  7 pull requests submitted:
  - Hook into Permissions API to get permission (by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/68 
  - Only update position if document is showing (by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/67 
  - Editorial: recipients are not a conformance class (by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/66 
  - Editorial: call out examples more clearly + add explainer (by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/65 
  - MUST have express permission to share location (by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/64 
  - Editorial: remove RFC2119 words from Requirements (by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/63 
  - Default errorCallback to null (by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/62 

  4 pull requests received 12 new comments:
  - #67 Only update position if document is showing (1 by marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/67 
  - #65 Editorial: call out examples more clearly + add explainer (4 by marcoscaceres, xfq)
    https://github.com/w3c/geolocation-api/pull/65 
  - #64 MUST have express permission to share location (2 by marcoscaceres, reillyeon)
    https://github.com/w3c/geolocation-api/pull/64 
  - #62 Default errorCallback to null (5 by cdumez, marcoscaceres)
    https://github.com/w3c/geolocation-api/pull/62 

  3 pull requests merged:
  - Editorial: remove RFC2119 words from Requirements
    https://github.com/w3c/geolocation-api/pull/63 
  - Default errorCallback to null
    https://github.com/w3c/geolocation-api/pull/62 
  - Editorial: fix up .message text
    https://github.com/w3c/geolocation-api/pull/51 

* w3c/screen-wake-lock (+1/-1/💬5)
  1 pull requests submitted:
  - Update auto-releasing wake lock examples (by anssiko)
    https://github.com/w3c/screen-wake-lock/pull/310 

  2 pull requests received 5 new comments:
  - #307 Clean up task queuing and document management (1 by rakuco)
    https://github.com/w3c/screen-wake-lock/pull/307 
  - #299 editorial: Tidy up uses of "in parallel". (4 by marcoscaceres, rakuco)
    https://github.com/w3c/screen-wake-lock/pull/299 

  1 pull requests merged:
  - editorial: Tidy up uses of "in parallel".
    https://github.com/w3c/screen-wake-lock/pull/299 


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/deviceorientation
* https://github.com/w3c/geolocation-sensor
* https://github.com/w3c/geolocation-api
* https://github.com/w3c/motion-sensors
* https://github.com/w3c/battery
* https://github.com/w3c/screen-wake-lock
* https://github.com/w3c/system-wake-lock
* https://github.com/w3c/html-media-capture
* https://github.com/w3c/vibration
* https://github.com/w3c/dap-charter


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config