[geolocation-api] Pull Request: Correction: check for non-secure contexts
[geolocation-api] Non-secure context check vanished from the spec (#156)
Re: [deviceorientation] Accessibility Checklist (#131)
Closed: [deviceorientation] Accessibility Checklist (#131)
[geolocation-api] /TR/ missing from latest published version for ED (#155)
Re: [deviceorientation] Make DeviceMotionEventInit members nullable with null default (#141)
- Re: [deviceorientation] Make DeviceMotionEventInit members nullable with null default (#141)
- Re: [deviceorientation] Make DeviceMotionEventInit members nullable with null default (#141)
[deviceorientation] Goodies from Accelerometer, Motion, Orientation, Gyro specs to bring over (#186)
Re: [deviceorientation] Guidance needed: how to acquire compass headings in a future-compatible manner? (#137)
Re: [deviceorientation] How to check when permission is denied? (#148)
- Re: [deviceorientation] How to check when permission is denied? (#148)
- Re: [deviceorientation] How to check when permission is denied? (#148)
[deviceorientation] Interval seems confusing (#185)
- Re: [deviceorientation] Interval seems confusing (#185)
- Re: [deviceorientation] Interval seems confusing (#185)
- Re: [deviceorientation] How reliable is interval? (#185)
- Re: [deviceorientation] How reliable is interval? (#185)
[deviceorientation] fire an orientation event need to use the dictionary (#184)
[deviceorientation] Combine permission request is problematic (#183)
- Re: [deviceorientation] Combined permission request is problematic (#183)
- Re: [deviceorientation] Combined permission request is problematic (#183)
- Re: [deviceorientation] Combined permission request is problematic (#183)
- Re: [deviceorientation] Combined permission request is problematic (#183)
- Re: [deviceorientation] Combined permission request is problematic (#183)
[deviceorientation] Alternative orientation representations? (#182)
- Re: [deviceorientation] Alternative orientation representations? (#182)
- Re: [deviceorientation] Alternative orientation representations? (#182)
- Re: [deviceorientation] Alternative orientation representations? (#182)
[deviceorientation] Fully active checks (#181)
[deviceorientation] Abstract away underlying sensors (#180)
- Re: [deviceorientation] Abstract away underlying sensors (#180)
- Re: [deviceorientation] Abstract away underlying sensors (#180)
[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)
- Re: [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)
- Re: [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)
Re: [geolocation-api] Alignment with Geo-alignment/GeoPose? (#130)
[geolocation-api] Pull Request: Update geolocation acquisition algorithm to explicitly define data types and handle cached positions
- Re: [geolocation-api] Update geolocation acquisition algorithm to explicitly 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] Support floorLevel on GeolocationCoordinates? (#122)
[deviceorientation] Pull Request: chore: fix link in CONTRIBUTING.md
[deviceorientation] Pull Request: chore: Update README.md
- Re: [deviceorientation] chore: Update README.md (#178)
- Re: [deviceorientation] chore: Update README.md (#178)
- Re: [deviceorientation] chore: Update README.md (#178)
[deviceorientation] Pull Request: Editorial: simplify parse orientation data reading algo
[deviceorientation] Pull Request: Editorial: use bikeshed shorthands for devicemotion firing steps
[deviceorientation] Pull Request: Editorial: use bikeshed shorthands in requestPermission() algorithm
[deviceorientation] Pull Request: Editorial: more bikeshed shorthand usage
[deviceorientation] Pull Request: Editorial: simplify "significant change in orientation" algorithm
[deviceorientation] Pull Request: Editorial: use more bikeshed shorthands
[deviceorientation] Pull Request: Editorial: cleanup fire an orientation event algorithm
[deviceorientation] Pull Request: Editorial: cleanup requestPermission() algorithm
Re: [deviceorientation] Security/privacy consideration: cross-origin linkage (#33)
[deviceorientation] Pull Request: Editorial: rewrite abstract
[deviceorientation] Pull Request: Editorial: change spec title
[deviceorientation] Pull Request: Editorial: use bikeshed shorthands for task source section
[deviceorientation] Pull Request: Chore: enable markdown shorthands in index.bs
- Re: [deviceorientation] Chore: enable markdown shorthands in index.bs (#166)
- Re: [deviceorientation] Chore: enable markdown shorthands in index.bs (#166)
- Re: [deviceorientation] Chore: enable markdown shorthands in index.bs (#166)
[deviceorientation] Pull Request: Editorial: rewrite permissions section
- Re: [deviceorientation] Editorial: rewrite permissions section (#165)
- Re: [deviceorientation] Editorial: rewrite permissions section (#165)
[deviceorientation] Pull Request: Editorial: fix allowlist 'self' cross reference
[deviceorientation] Pull Request: Editorials: small fixup to Device Motion section
[deviceorientation] Do we really need 3 permissions policies? (#162)
- Re: [deviceorientation] Do we really need 3 permissions policies? (#162)
- Re: [deviceorientation] Do we really need 3 permissions policies? (#162)
- Re: [deviceorientation] Do we really need 3 permissions policies? (#162)
- Re: [deviceorientation] Do we really need 3 permissions policies? (#162)
- Re: [deviceorientation] Do we really need 3 permissions policies? (#162)
- Re: [deviceorientation] Do we really need 3 permissions policies? (#162)
- Re: [deviceorientation] Do we really need 3 permissions policies? (#162)
[deviceorientation] Pull Request: Editorial: drop Changes section
- Re: [deviceorientation] Editorial: drop Changes section (#161)
- Re: [deviceorientation] Editorial: drop Changes section (#161)
- Re: [deviceorientation] Editorial: drop Changes section (#161)
[deviceorientation] Pull Request: Editorial: contextualize x, y, z in model a bit more
[deviceorientation] Pull Request: Editorial: drop Use cases and Requirements section
[deviceorientation] Pull Request: Editorial: rework scope
[deviceorientation] Pull Request: Editorial: fixup/modernize examples
[deviceorientation] Pull Request: Editorial: reword the iIntroduction section
[deviceorientation] Pull Request: Editorial: automatically generate the conformance section
- Re: [deviceorientation] Editorial: automatically generate the conformance section (#155)
- Re: [deviceorientation] Editorial: automatically generate the conformance section (#155)