[
https://issues.apache.org/jira/browse/CB-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043548#comment-14043548
]
Joe Bowser commented on CB-5977:
--------------------------------
So, I don't know where the support person got that information, but that's not
accurate.
There were numerous reasons to get rid of the Geolocation Plugin code on
Android:
* It didn't work well
* It wasn't compliant (it was either Towers or GPS, not both)
* The Browser Geolocation worked better
* The browser geolocation was actually complaint with W3C specification
* Less code is better
I'm not sure what you mean by CordovaNavigator. Unlike iOS, we don't clobber
nagivator. Android 2.3+ has had Geolocation in the browser, and it's always
worked better than our geolocation. The only thing we do is install the proper
permissions. It's possible you have old JS that's messing with the default
geolocation code, however we've never seen a problem with it in any of our
tests.
> Deprecate Android Geolocation plugin
> -------------------------------------
>
> Key: CB-5977
> URL: https://issues.apache.org/jira/browse/CB-5977
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin Geolocation
> Reporter: Mike Billau
> Assignee: Joe Bowser
> Fix For: 3.5.0
>
>
> Lets deprecate the Geolocation plugin on Android since the Web Geolocation
> works just as well as our implementation. See
> http://markmail.org/message/ketdgrzm2dcpxfo2 for further discussion.
> We need to keep the config.xml in order to continue adding the location
> permissions. We should zero out the rest of the code since it shouldn't be
> used.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
