I don't suspect that window.close will cause a problem - but we have to know how various js frameworks will react and do testing when hijacking. Also, we need to take a look at expected behavior either by spec or common use. We overrode history in 0.9.6 or 1.0 timeframe. Regular PhoneGap apps worked fine, but turns out that it broke jQuery (Since we don't use jQuery, we found out via the forums). So the intent is to determine if there are any gotcha's for a particular solution.
There was discussion around integrating childbrowser in base, and loadUrl morphed into that for Android. Most of the code already existed in DroidGap, so this was a simple extension to wrap the functionality. This is used to load urls in the PhoneGap webview plus launch in separate browser, depending upon whitelist url, protocol, etc. Users can register for backbutton events, however, the register event method is hooked (phonegap.js.base) and actually calls App overrideBackButton method. If there's a web way to do this, then that's great, but I'm not aware of anything on Android. The Device.* methods that Drew mentioned are all deprecated and should be removed. On Tue, Jan 31, 2012 at 3:07 PM, Drew Walters <deedu...@gmail.com> wrote: > Should the following be wacked too? > > Device.overrideBackButton > Device.exitApp > Device.resetBackButton > > On Tue, Jan 31, 2012 at 2:11 PM, Simon MacDonald > <simon.macdon...@gmail.com>wrote: > > > On Tue, Jan 31, 2012 at 3:04 PM, Filip Maj <f...@adobe.com> wrote: > > > > > > > > >*overrideBackButton* - Imma gonna take this out right now. This is a > > > >legacy > > > >piece of code. The proper way of doing this is to register an event > > > >listener for the "backbuttton" event. > > > > > > Yeh in Cordova-js this is done in a "standard" way - no need for native > > > magiks. > > > > > > > > It's gone. Change already pushed to the Apache GIT repo. > > > > Simon Mac Donald > > http://hi.im/simonmacdonald > > >
