Re: CfC to publish Geolocation API as Proposed Recommendation - review by 23 Mar 2022

Hi DAS WG,
FYI PING,

This CfC passed.

An implementation report is at (thanks Marcos!):

https://w3c.github.io/geolocation-api/reports/PR_imp_report.html


Please note the assertions that are not testable mentioned in the report.

From a WG’s point of view, the specification satisfies the PR transition requirements.

Thanks,

-Anssi (DAS WG co-chair)


On 9. Mar 2022, at 15.26, Kostiainen, Anssi <anssi.kostiainen@intel.com<mailto:anssi.kostiainen@intel.com>> wrote:

Hi DAS WG,
FYI PING,

This is a Call for Consensus (CfC) to publish the Geolocation API as a Proposed Recommendation, using the latest Candidate Recommendation Draft [1] as the basis.

No substantive changes to the document have been made since the most recent Candidate Recommendation Snapshot published 17 February 2022. See the publication history at [2].

W3C Process sets forth the requirements for transitioning to Proposed Recommendation [3]. The following requirement needs special consideration from the Working Group participants and key stakeholders for the reasons outlined below:

"Must show adequate implementation experience except where an exception is approved by the Director.”

Geolocation API test suite [4] depends on certain features of the WebDriver browser automation framework only implemented in Chromium. Due to this, the test report [5] currently shows a substantial number of test failures. We expect the currently reported Chrome and Edge test failures to be fixed prior to transition to Proposed Recommendation, but we do not expect Firefox and Safari to implement the said WebDriver features in time for this Proposed Recommendation transition due to substantial amount of work. To that end, we plan to seek an exception from the Director for the Proposed Recommendation transition when we are able to demonstrate that the ideally fully automated tests pass on Chromium-based browsers and are able to demonstrate interoperability with Firefox and Safari by other means, for example, manual testing.

For more details on the test failures, please see [6].

Please review the specification and this proposed transition plan and submit any comments or questions you may have by replying to this mail by 23 Mar 2022.

Thanks,

-Anssi (DAS WG co-chair)

[1] https://www.w3.org/TR/geolocation/

[2] https://www.w3.org/standards/history/geolocation

[3] https://www.w3.org/2021/Process-20211102/#transition-pr
[4] https://github.com/web-platform-tests/wpt/tree/master/geolocation-API

[5] https://wpt.fyi/geolocation-API

[6] https://github.com/w3c/geolocation-api/issues/121