+1 to nuking it. Anyone depending on it for really old versions of Android is likely not doing anyone a favor (themselves or their users) - and (I think) it adds to new developer confusion. Then again, having a plugin that only adds the permission bit sort of does that too.
On Fri, Jan 10, 2014 at 7:26 PM, Michal Mocny <mmo...@chromium.org> wrote: > Adding support for play services based geolocation could come as a value > add later. If the current implementation is broken and no one wants to > work on it (seems to be the case since it hasn't been fixed yet), then > Joe's suggestion to just drop it now and leave a no-op plugin that adds > permission only sounds like the right thing short term. > > Joes first email claims Web Geolocation supports all current versions of > android (http://caniuse.com/geolocation claims android 2.1+ though I > didn't > look in to possible quirks). > > -Michal > > > On Fri, Jan 10, 2014 at 8:43 PM, Andrew Grieve <agri...@chromium.org> > wrote: > > > Is the plugin still needed on older android versions? e.g. we might > > want to have it be a no-op based on the android version instead of > > deleting it? > > > > Android geolocation seems to have gone Play Services, so another > > option would be to make the plugin use that instead of the OS > > geolocation in order to provide some utility. > > > > On Fri, Jan 10, 2014 at 4:14 PM, Jesse <purplecabb...@gmail.com> wrote: > > > The index.html issue was iOS, not sure if it still exists. > > > > > > Windows Phone 7+8 use the browser based geolocation as they have > > > implemented the spec, However because of the way permissions are > > managed, > > > there is a native do-nothing stub that simply signal that Location > > Services > > > are required. > > > Windows8 does some massaging of the api to the WinJS version, and adds > > the > > > permissions to the project. > > > > > > I just spoke ( physically ) with Joe, and with this change, the > > geolocation > > > plugin would still exist for Android, it would just add the permission > to > > > the app. So, Android's plugin would be almost identical to WP7+8 with > > this > > > change. > > > > > > +1 from me, assuming everything will just work. > > > > > > > > > > > > @purplecabbage > > > risingj.com > > > > > > > > > On Fri, Jan 10, 2014 at 3:40 PM, Joe Bowser <bows...@gmail.com> wrote: > > > > > >> It never did on Android, you can see this in Mobile-Spec. > > >> > > >> On Fri, Jan 10, 2014 at 3:39 PM, Brian LeRoux <b...@brian.io> wrote: > > >> > Does the permission dialogue still ask for index.html ? > > >> > > > >> > > > >> > On Friday, January 10, 2014, Joe Bowser wrote: > > >> >> > > >> >> Due to numerous issues found in Geolocation, combined with an > > increase > > >> >> in reliability of the Web Geolocation, I'm wanting to see us EOL > the > > >> >> Geolocation plugin. > > >> >> > > >> >> Reasons for this include: > > >> >> * Support for Geolocation on all currently supported versions of > > >> Android > > >> >> * Numerous issues with the current Geolocation plugin that may > > >> >> involve a full re-write of the Geolocation plugins. > > >> >> * The Web Geolocation may be more energy efficient than our own > > >> >> Geolocation polling. > > >> >> > > >> >> What do people think about deprecating this plugin and recommending > > >> >> that we use the browser's implementation on Android? > > >> >> > > >> >> Joe > > >> > > >
