Re: [deviceorientation] Guidance needed: how to acquire compass headings in a future-compatible manner? (#137)
Re: [deviceorientation] Make DeviceMotionEventInit members nullable with null default (#141)
Re: [deviceorientation] How to check when permission is denied? (#148)
Re: [deviceorientation] Combined permission request is problematic (#183)
Re: [deviceorientation] Alternative orientation representations? (#182)
Re: [deviceorientation] fire an orientation event need to use the dictionary (#184)
Closed: [geolocation-api] repo name nit: it'd be nice if this were simply w3c/geolocation (#154)
Re: [geolocation-api] repo name nit: it'd be nice if this were simply w3c/geolocation (#154)
[geolocation-api] Update implementation report (#163)
[geolocation-api] Pull Request: Addition: Define units for accuracy
[geolocation-api] Pull Request: Editorial: Minor corrections prior to republication
[geolocation-api] Define the units of `accuracy` (#160)
[geolocation-api] Pull Request: minor text fix, for pubrules
Closed: [geolocation-api] /TR/ missing from latest published version for ED (#155)
[geolocation-api] Pull Request: Disable /TR/ publication for errata.html
- Re: [geolocation-api] Disable /TR/ publication for errata.html (#158)
- Re: [geolocation-api] Disable /TR/ publication for errata.html (#158)
- Re: [geolocation-api] Disable /TR/ publication for errata.html (#158)
- Re: [geolocation-api] Disable /TR/ publication for errata.html (#158)
- Re: [geolocation-api] Disable /TR/ publication for errata.html (#158)
Re: [geolocation-api] Correction: Update acquisition algorithm to define data types and handle cached positions (#153)
- Re: [geolocation-api] Correction: Update acquisition algorithm to define data types and handle cached positions (#153)
- Re: [geolocation-api] Correction: Update acquisition algorithm to define data types and handle cached positions (#153)