- From: <sysbot+notifier@w3.org>
- Date: Mon, 07 Mar 2022 00:19:48 +0000
- To: public-transition-announce@w3.org
PR Request for Geolocation API from https://github.com/w3c/transitions/issues/417 # Document title, URLs, estimated publication date Geolocation API ?? March 2022 Ed: https://w3c.github.io/geolocation-api/ TR: https://www.w3.org/TR/geolocation/ # Abstract https://w3c.github.io/geolocation-api/#abstract # Status https://www.w3.org/TR/geolocation/#sotd # Will new features be allowed to be incorporated in the Recommendation? Yes # Link to group's decision to request transition https://github.com/w3c/geolocation-api/issues/121 # Changes None. # Requirements satisfied Yes. # Dependencies met (or not) Yes. # Wide Review Done in CR. # Issues addressed None. # Formal Objections None (...so far). # Implementation Gecko, WebKit, and Chromium. Report: https://wpt.fyi/geolocation-API There is an unrelated bug in Chrome that is preventing Geolocation permission from being "granted". This is making it look like there are more failures than there actually are. Similarly, the Web Driven API the tests depend on is not implemented in Firefox or Safari (thus they show up as failures). However, running the tests manually, the tests pass. We can also provide links to patches that show that everything is implemented per spec. # Patent disclosures None. -- This email was generated automatically using https://github.com/w3c/transition-issues-bot
Received on Monday, 7 March 2022 00:19:53 UTC