[compute-pressure] Metabug: Raising Specification to CR maturity level. (#295)
[compute-pressure] Tag "thermals" sources as "at_risk" in specification (#294)
- Closed: [compute-pressure] Tag "thermals" source as "at_risk" in specification (#294)
- Re: [compute-pressure] Tag "thermals" source as "at_risk" in specification (#294)
Re: [device-posture] Internationalization checklist (#148)
Closed: [device-posture] Internationalization checklist (#148)
Re: [accelerometer] device calibration of accelerometers may reveal precise hardware fingerprint (#54)
Closed: [accelerometer] device calibration of accelerometers may reveal precise hardware fingerprint (#54)
Re: [gyroscope] define normative privacy mitigation(s) (#45)
Re: [accelerometer] define normative privacy mitigation (#57)
Re: [accelerometer] Disable Accelerometer use while Vibration API is in use (#69)
Re: [sensors] [Meta] Proof-read and modernize spec (#463)
Re: [screen-wake-lock] Should this prompt? (#324)
Re: [screen-wake-lock] Distinguish exceptions on .request() (#352)
Re: [screen-wake-lock] Require transient activation to request lock (#350)
- Re: [screen-wake-lock] Require transient activation to request lock (#350)
- Re: [screen-wake-lock] Require transient activation to request lock (#350)
Re: [device-posture] Grammar: change "a hands-free" to "a hands-free experience" (#161)
Re: [device-posture] Should Device Posture API be exposed to iframes (JS or CSS) (#111)
Closed: [compute-pressure] "Current pressure state" definition and cardinality are confusing (#281)
Re: [compute-pressure] Does compute pressure reflect OS-level speed limit changes due to throttling? (#228)
- Re: [compute-pressure] Does compute pressure reflect OS-level speed limit changes due to throttling? (#228)
- Re: [compute-pressure] Does compute pressure reflect OS-level speed limit changes due to throttling? (#228)
Re: [sensors] Sensor discovery (#7)
Re: [compute-pressure] Use-case: provide a battery draining rate indication for application (#126)
Closed: [compute-pressure] Use-case: provide a battery draining rate indication for application (#126)
Re: [vibration] Update spec metadata and add Changes section (#44)
Closed: [device-posture] Device posture and direction interaction (#151)
Re: [device-posture] Add feedback from i18n W3C review. (#160)
Re: [device-posture] Device posture and direction interaction (#151)
Re: [compute-pressure] Wide review tracker (#177)
- Re: [compute-pressure] Wide review tracker (#177)
- Re: [compute-pressure] Wide review tracker (#177)
- Re: [compute-pressure] Wide review tracker (#177)
- Re: [compute-pressure] Wide review tracker (#177)
Re: [vibration] Update implementation report (#33)
[geolocation-sensor] Missing tasks in parallel steps in Geolocation Sensor (#63)
Re: [vibration] turn page-visibility-2 into WHATWG/HTML (#41)
Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22)
- Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22)
- Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22)
- Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22)
- Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22)
- Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22)
[compute-pressure] "Rate-limiting change notifications" section is confusing (#291)
- Re: [compute-pressure] "Rate-limiting change notifications" section is confusing (#291)
- Re: [compute-pressure] "Rate-limiting change notifications" section is confusing (#291)
- Re: [compute-pressure] "Rate-limiting change notifications" section is confusing (#291)
- Re: [compute-pressure] "Rate-limiting change notifications" section is confusing (#291)