Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of gtanner@gmail.com designates
 209.85.223.175 as permitted sender)
Subject: Re: InAppBrowser api questions
References: 
 <CAE6O_-ZsorWN8Hu-d68zGMx6QQPb_Ww71q=QjWxZ_jjpsUgiuw@mail.gmail.com>
 <CAHauEQ6pzELmh7fhMYSn0HVZFk9ia5E_G=fTnDua=Rz4jsT=9w@mail.gmail.com>
From: Gord Tanner <gtanner@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: 
 <CAHauEQ6pzELmh7fhMYSn0HVZFk9ia5E_G=fTnDua=Rz4jsT=9w@mail.gmail.com>
Message-Id: <206D8B05-3F94-4CFF-83C8-5F58188A1C89@gmail.com>
Date: Fri, 9 Nov 2012 18:02:23 -0500
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Nice!!!

When is the next release? I will create a jira to track looking into getting=
 the child browser plugin working for Cordova once the bb10 API is available=


On 2012-11-09, at 3:24 PM, Nukul Bhasin <me@nukulb.com> wrote:

> BB10 WebWorks implements something similar. It will be a part of the next
> release
>=20
> here is the definition for what we implemented for BB10
>=20
> https://github.com/blackberry/BB10-WebWorks-Framework/issues/230
>=20
>=20
> On Fri, Nov 9, 2012 at 12:43 PM, Shazron <shazron@gmail.com> wrote:
>=20
>> WIki page: http://wiki.apache.org/cordova/InAppBrowser
>> Some questions brought up by Jesse in JIRA (replicated below):
>> http://goo.gl/cZe84
>>=20
>> ----------------------------------------------------
>> Jesse MacFadyen:
>>=20
>> I have some open questions about the wiki defined 'spec'
>>=20
>> 1. window.open('http://random-url.com', '_self'); // loads in InAppBrowse=
r
>>    so even though the random-url is not whitelisted, it is permitted to
>> load within the application, inside the InAppBrowser. This is currently n=
ot
>> trivial on iOS.
>>=20
>> 2. How can I open a whitelisted url in the native browser? ie. mobile
>> safari
>>    there is no clear path to targeting ALL 3 possibilities or a)the app
>> page, b) the InAppBrowser, c) the system browser ( for a whitelisted URL )=

>>    it makes sense that you cannot open a file:// url in the system browse=
r
>> + you cannot open a non-whitelisted url in the app.
>>=20
>> ----------------------------------------------------
>>=20
>> My comments:
>>=20
>> 1. This as Jesse points out, is not trivial on iOS. The "easy way" would b=
e
>> to not allow this, but kick it out to the system browser (Mobile Safari),=

>> and have that as a general rule, any non-whitelisted URLs for the
>> InAppBrowser are kicked out to the system browser. I don't know how hard i=
t
>> is for Android.
>>=20
>> If we were to do this, we would have to temporarily allow the url to bypa=
ss
>> the whitelist which could be kludgy (since we can't know what other URLs
>> that URL will load) -- essentially this issue
>> http://issues.cordova.io/1695would totally solve this correctly, but
>> we don't have a solution yet for
>> that issue.
>>=20
>> 2. This case has not been addressed. I would think _blank would be the ca=
se
>> but this is specified as the InAppBrowser here. How about this case, we
>> could use _parent for InAppBrowser, but _blank for system browser? Howeve=
r,
>> this would not be consistent with how the other calls are specified (unle=
ss
>> we change the others to be consistent).
>>=20
>> Another possible solution is to kick out to the system browser if an
>> unknown value is used (some random value), that will use the system
>> browser, which is consistent with how window.open works.
>=20
>=20
>=20
> --=20
> *Nukul Bhasin*
> *Computer Engineer, B.Eng*
> *10 Queens Quay W, suite#1710*
> *Toronto, ON, Canada*
> *Ph: 416 508 3157*