Thursday, 20 August 2020
- Re: [deviceorientation] Drop duplicate PermissionState definition (#88)
- Re: [deviceorientation] Drop duplicate PermissionState definition (#88)
Tuesday, 18 August 2020
Friday, 14 August 2020
Wednesday, 12 August 2020
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
Tuesday, 11 August 2020
- Re: [geolocation-api] Security review: General observations (#57)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
- Re: [geolocation-api] How to specify desired accuracy / resolution of data? (#49)
- Re: [geolocation-api] [meta] Wide review tracker (#43)
- Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56)
- Re: [geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
- Closed: [geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
Monday, 10 August 2020
- Re: [geolocation-api] Security review: General observations (#57)
- Re: [geolocation-api] Section 6: Non-normative but containing implementation requirements? (#56)
- Re: [geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
- Re: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)
- Re: [geolocation-api] Section 1: Editorial - possible syntax error (#53)
- Closed: [geolocation-api] Section 1: Editorial - possible syntax error (#53)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- Re: [deviceorientation] Move fingerprintable APIs behind permissions (#85)
- [geolocation-api] Security review: General observations (#57)
- [geolocation-api] Sectioni 6: Non-normative but implementation requirements? (#56)
- [geolocation-api] Section 4.5.6: Value for speed for stationary device (#55)
- [geolocation-api] Why only "SHOULD" for protection of privacy? (#54)
- [geolocation-api] Editorial - possible syntax error (#53)
Friday, 7 August 2020
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)
- Re: [geolocation-api] Change text for description of GeolocationPositionError.message attribute (#50)