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 2D93F1768C for ; Fri, 29 Jan 2016 16:29:30 +0000 (UTC) Received: (qmail 44836 invoked by uid 500); 29 Jan 2016 16:29:29 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 44802 invoked by uid 500); 29 Jan 2016 16:29:29 -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 44759 invoked by uid 99); 29 Jan 2016 16:29:29 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jan 2016 16:29:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D552BC01AA for ; Fri, 29 Jan 2016 16:29:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.149 X-Spam-Level: *** X-Spam-Status: No, score=3.149 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=3, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id OpFjbCxOKDRL for ; Fri, 29 Jan 2016 16:29:13 +0000 (UTC) Received: from mail-vk0-f41.google.com (mail-vk0-f41.google.com [209.85.213.41]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 6AB7B43F64 for ; Fri, 29 Jan 2016 16:29:13 +0000 (UTC) Received: by mail-vk0-f41.google.com with SMTP id n1so44717539vkb.3 for ; Fri, 29 Jan 2016 08:29:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=wewwolDmFB/m4pcQoFUU6Kvit0pILtko3e+69XxUS00=; b=qTx0hS5dnrz9SIUbBLOihz3BRZHqR4p8Nbi5rIW6/sY3ZL9Eu038VRnpDwr9ZdHn7o kxZD+tO7XWcDZMhhC8/nPDKhmtFkEbdPrG1gCqVjNqSoomEBh5/6D4PIcuNnm8G5Zr+V Q4CORkhQEEaCmqiC951RI1Z/D4kfdpzdd+x3ezfGy+5UVP7FTL9p5UVOA5KgCOhqm86+ 4UruneJB4JZfrsb+LetkTQkygrCCXc6GnpwL4Dhtu0lcD7lyW4ZdBitdRGbTkZVVpUI8 7JzXtTCuJQEZgNVumZC/fmD5oT4Vr7lRVSisHyScndMlGN1V0b3xTtLT2aKcafSDYwvD 1U5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=wewwolDmFB/m4pcQoFUU6Kvit0pILtko3e+69XxUS00=; b=b2v05bwuecbbEGYnPQ/3NwXluD4eK4I2Ooi78U33p9DIvdp3ctTrhEs1tarAhDt8lE vrsbqCxGfhjQorV1gxxUlPWbLF4DbYYHdM2Zs2jhmzR9lx6Jtto9+RiakRsIquDY16NY xtxslh4yYENecEugjFKo303gxGGw/bwAIG1MG1BC4PN+UCbp8rk1uHqmc+Azk3QMY4DI GuTbnms64LNaZNcdOsUeQjyFdX+8xZUS5ZBGkQZ9RlYSHfwSNXlU9rttmrdv9gaKekhh p6uEj+O94orK/iXvcwjagHolwnioPKXaGmZ9ypqzQPyvt/AAh4Bz1tAySEdbGK9lVqGY Et9w== X-Gm-Message-State: AG10YOT9qjkRj88A3uBFUIEW3WZRJo1ClJhhcvGDATDl5rYd+C98kEx8yI9/0lkk7PdQkdYBsp2hsmfmrJe5Dg== X-Received: by 10.31.132.140 with SMTP id g134mr6511316vkd.94.1454084947450; Fri, 29 Jan 2016 08:29:07 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Carlos Santana Date: Fri, 29 Jan 2016 16:28:57 +0000 Message-ID: Subject: Re: geolocation getCurrentPosition and disabled location services To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=001a1145886ec42176052a7b8813 --001a1145886ec42176052a7b8813 Content-Type: text/plain; charset=UTF-8 I see so there is an API to force the OS dialog? it would be another option in geolocationOptions, and would be only and iOS Quirk type of thing. I think we decided that moving forward that we should stay away of implementing things for a single platform. On Fri, Jan 29, 2016 at 10:14 AM julio cesar sanchez wrote: > Carlos, the message he is talking about is a system message, so we don't > have to worry about how it works or the message it has to show. > It's displayed automatically when you call [self.locationManager > startUpdatingLocation]; and the geolocation services are turned off, but > the current implementation of the plugin doesn't call [self.locationManager > startUpdatingLocation]; if the permissions are turned off. > > Bad thing is geolocation plugin follows the W3C API, and I don't see any > way of adding this option without "breaking" the API > > 2016-01-29 14:18 GMT+01:00 Carlos Santana : > > > Thanks for opening the JIRA that says a lot about your interest to help. > > But my opinion the request is for a specific implementation related to > > UI/UX, then what would the dialog say and how to handle language etc... > > > > This is the reason in core Cordova we try to stay away from providing > > specific UI implementations > > > > Also there is no native iOS API to open settings app in the specific > > section of Location Services that I'm aware. There are some APIs to go > the > > your app section but not the location services. > > > > I would consider the use case be concern of Dev space how to handle the > > UI/UX when our current API returns with permission denied > > On Fri, Jan 29, 2016 at 7:07 AM Zarko Hristovski > wrote: > > > > > Thanks. > > > > > > Created CB-10478 (getCurrentPosition should trigger system dialog for > > > enabling location services): > > > https://issues.apache.org/jira/browse/CB-10478 > > > > > > It's a feature request, so fingers crossed. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org > > > For additional commands, e-mail: dev-help@cordova.apache.org > > > > > > > > > --001a1145886ec42176052a7b8813--