Re: [geolocation-api] Transition to Proposed Recommendation (#121)

@marcoscaceres @reillyeon, does the following describe the situation accurately:

>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 automated tests pass on Chromium-based browsers and are able to demonstrate interoperability with Firefox and Safari by other means, for example, manual testing.

This is an excerpt I plan to include in the CfC to explain the situation to the Working Group and its key stakeholders.

The reason why I'm stressing this point is that the "adequate implementation experience" is tested as "must show" at Proposed Recommendation transition time and the AC will be asking the WG to show evidence when they are asked to review the Proposed Recommendation.

GitHub Notification of comment by anssiko
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 8 March 2022 08:19:12 UTC