Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of shazron@gmail.com designates
 209.85.212.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAM1AYQD8iehs=Z3QUrN6PvPCnJV+jx6vwfQHHotRCAk2yzwStA@mail.gmail.com>
References: 
 <CAE6O_-bpUAXdqfBNW00et4FVqWHKTV3k3Hy-PZTo28qKo5uyUw@mail.gmail.com>
	<CABiQX1XYHpVAmbDM_OPzbFyLQNd1363S5jRWWq=ABiWt+V5q-A@mail.gmail.com>
	<CAE6O_-ZpnCTS76xB8U4LObJe+iJn-FmK9deuC_bpR7j1UpTeiw@mail.gmail.com>
	<CABiQX1U+=u+_OGnyrJRMx9OCn0iQoZmVK4NiZ0cSX0-OPP22_g@mail.gmail.com>
	<CAE6O_-b8gqWhCHj9FLMszcNoeap=GJCUsGecf8ahLVFXDCT6Gg@mail.gmail.com>
	<CAM1AYQD8iehs=Z3QUrN6PvPCnJV+jx6vwfQHHotRCAk2yzwStA@mail.gmail.com>
Date: Thu, 22 Nov 2012 20:50:01 -0800
Message-ID: 
 <CAE6O_-Y7YyTKhAsmDgb-XimRngbE4gWxpi+KyvrrzaMvb0Ejow@mail.gmail.com>
Subject: Re: InAppBrowser - events
From: Shazron <shazron@gmail.com>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=089e0115e9d407df7604cf225164

--089e0115e9d407df7604cf225164
Content-Type: text/plain; charset=ISO-8859-1

I'd like to, if everyone agrees. I'd like to wipe out ChildBrowser use if I
can, and this (events) is the only thing I believe that people are still
using ChilBrowser for.
Is this required for the 2.3.0 release?

Simon Mac Donald
http://hi.im/simonmacdonald


On Wed, Nov 21, 2012 at 11:30 PM, Shazron <shazron@gmail.com> wrote:

> Great! Let's stick with one API, since we have Chrome members on the
> Cordova team the choice is obvious :)
>
>
> On Wed, Nov 21, 2012 at 8:06 PM, Andrew Grieve <agrieve@chromium.org>
> wrote:
>
> > Looks that way. Given how similar they are, I don't think it matters
> which
> > one we go with (or if we come up with our own event names), but it'd be
> > good to follow the same pattern of having events and an API like
> > canGoBack(), goForward(), etc. If they ever move to standardize, then we
> > can follow suit.
> >
> >
> > On Wed, Nov 21, 2012 at 7:18 PM, Shazron <shazron@gmail.com> wrote:
> >
> > > Mozilla's 'locationchange' is similar to what we have for
ChildBrowser,
> > but
> > > I don't see the equivalent in the Chrome example - I suppose it is
> > > 'loadstop'?
> > >
> > > I suppose if we were to adopt either, it would go something like this:
> > >
> > > var iab = window.open('http://apache.org', '_blank');
> > > // Firefox
> > > iab.addEventListener('locationchange', handleLocationChange);
> > > // Chrome
> > > iab.addEventListener('loadstop', handleLoadStop);
> > >
> > > // Firefox
> > > function handleLocationChange(e) {
> > >      console.log('location changed to: ' + e.detail);
> > > }
> > > // Chrome
> > > function handleLoadStop(e) {
> > >      console.log('location changed to: ' + e.url);
> > > }
> > >
> > > On Wed, Nov 21, 2012 at 1:32 PM, Andrew Grieve <agrieve@chromium.org>
> > > wrote:
> > >
> > > >
> > > >
> > >
> >
>
https://github.com/GoogleChrome/chrome-app-samples/blob/master/browser/browser.js
> > >
> >
>

--089e0115e9d407df7604cf225164--