Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EEBF410BE0 for ; Sat, 11 Jan 2014 01:44:32 +0000 (UTC) Received: (qmail 8645 invoked by uid 500); 11 Jan 2014 01:44:32 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 8617 invoked by uid 500); 11 Jan 2014 01:44:32 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 8609 invoked by uid 99); 11 Jan 2014 01:44:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 01:44:32 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates 209.85.192.179 as permitted sender) Received: from [209.85.192.179] (HELO mail-pd0-f179.google.com) (209.85.192.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 01:44:26 +0000 Received: by mail-pd0-f179.google.com with SMTP id y13so2753369pdi.38 for ; Fri, 10 Jan 2014 17:44:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=3gNpgYWmz79Hgy9x8xY/tkeWhpHgtynRGY+y4bkq3co=; b=ims7VHIM1gnWl13cotzL11a3u9JR6cmNWFiL5oZuofnwpGkTrDyt7biyfq/vFk1Geo nqMXKj2w98PIB7PHozivl4CJQpTGHUvtEd3fvTz1xxtAW3gfjWvBJkvmjw51ZGlA2xp8 Ffr23oYrpyUrN9mweMgbjMjgTRsGbX8FFL7AY7cQMVTAk9qjAAsOqBwoIQH1SpEEA/S3 NYdKZZIoV/xveCmYGg5Nqa/uy+ItMrP5jF2RMUzJMlFpjJlyHHUjwPfA3kHq7KrL5Vlp 3crPnve9o7lJRkryNnuyMaAShuwZvvSMVvorn4+4L8x0/NUjo04fW+tEgBey3X0Rzwnc M14Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=3gNpgYWmz79Hgy9x8xY/tkeWhpHgtynRGY+y4bkq3co=; b=Qr0c8ORzdq2KXup5eSI6dKWb4GY0dIZn3RDdMvWBO6ABvafzLPszmNi0LZmxW6Zqhp FyI0yD8HYvDu4JqthyjrXLz4fMVdF8QBxQmi3arGmPsGDe3lKuzpgxiWzf+4twPQ49N4 gJacGZ4+4S+Syl+K8uaYMYMIg0mwClOkEnlsQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=3gNpgYWmz79Hgy9x8xY/tkeWhpHgtynRGY+y4bkq3co=; b=CJsiSxmU39sToPWzp4wpfrn1DAdRc/siFDoQpvDwi10nNGNfildidndoW9QrNf0iNV xE1DINUKSIOdEgUO7ZM5aKri9Xa75epZmoAUPYR9inv/JzHTY5mLF0yTOtDulZos7pc3 VtKbFn4BRR0ALCjvViuKW3FPOtIi0tYLvLrzfb/98Ut3lpzLT/ucai8pNPRhDw2tJvPy p9Jg1EnLv2+gFVe/ss3Vub+QGGwU5qbFkxx2JsyiU8lZtMsKohgUSb5CuUgSsSGFAa9g ZWVgGLKdcuMbliqFG/fDHOzcy5Tar8HY6EgW8/CEv3QCf4FpkDoYkYiSfoTJxDR+svyj soiA== X-Gm-Message-State: ALoCoQnchxrgHEx8RIh0FZ9psoNTo25JQeMXXtevc2uJe0XNAmk8plW+wOOXHKcdHq3abr3xJXfRWs8z9TxTspOV5RiEUz5dCioqUbEuG4w7656OcXjZy3Y6T1otLSzR7PEYMkVUqXBxbFaZQ+GwfIAQ9pt6tUcIfWxG1LQZLGpGRKGE3Vk9Hnz76CEiUrR4b1B2yyq2+yREC/IN7Q5qxykhLnaCx47jyw== X-Received: by 10.68.17.41 with SMTP id l9mr15298146pbd.76.1389404645629; Fri, 10 Jan 2014 17:44:05 -0800 (PST) MIME-Version: 1.0 Sender: agrieve@google.com Received: by 10.68.130.198 with HTTP; Fri, 10 Jan 2014 17:43:45 -0800 (PST) In-Reply-To: References: From: Andrew Grieve Date: Fri, 10 Jan 2014 17:43:45 -0800 X-Google-Sender-Auth: az1S4vRRTdETyrXfYCggIXBEstM Message-ID: Subject: Re: [Android] Deprecation of Geolocation on Android To: dev Cc: "bowserj@apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org 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 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 wrote: > >> It never did on Android, you can see this in Mobile-Spec. >> >> On Fri, Jan 10, 2014 at 3:39 PM, Brian LeRoux 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 >>