public-geolocation@w3.org from November 2021 by subject

[deviceorientation] Drop duplicate PermissionState definition (#88)

[deviceorientation] Opposite z-axis for example 7 (#96)

[geolocation-api] Editorial: make use of HTML's page visibility change steps (#110)

[geolocation-api] Handle OS permission (#109)

[geolocation-api] Pull Request: chore(auto-publish.yml): enable experimental pubrules check

[geolocation-api] Pull Request: Editorial: make use of HTML's page visibility change steps

[geolocation-api] Pull Request: Handle OS permission

[geolocation-api] Pull Request: Suggest permission lifetimes

[geolocation-api] Pull Request: Tidied up document using tidy-html5

[geolocation-api] Republish as CR (#93)

[geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)

[geolocation-api] Specify behavior for operating system permissions (#107)

[geolocation-api] Suggest permission lifetimes? (#69)

[geolocation-api] Tidied up document using tidy-html5 (#112)

Closed: [deviceorientation] Opposite z-axis for example 7 (#96)

Closed: [geolocation-api] Republish as CR (#93)

Closed: [geolocation-api] Section 3: Why only "SHOULD" for protection of privacy? (#54)

Closed: [geolocation-api] Specify behavior for operating system permissions (#107)

Closed: [geolocation-api] Suggest permission lifetimes? (#69)

Last message date: Wednesday, 24 November 2021 01:18:36 UTC