Hide InAppBrowser bar with Done/History buttons

2,046 views
Skip to first unread message

Sönke Rohde

unread,
Feb 11, 2013, 1:16:22 PM2/11/13
to phon...@googlegroups.com
Couldn't find it in the docs.
How can we hide the bar at the bottom with the Done button and the history arrow buttons?

Thanks,
Sönke

Shazron

unread,
Feb 11, 2013, 2:54:49 PM2/11/13
to phonegap
You can't with the current implementation. If you could, how would you go "back" to your current view?


--
-- You received this message because you are subscribed to the Google
Groups "phonegap" group.
To post to this group, send email to phon...@googlegroups.com
To unsubscribe from this group, send email to
phonegap+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/phonegap?hl=en?hl=en
 
For more info on PhoneGap or to download the code go to www.phonegap.com
 
To compile in the cloud, check out build.phonegap.com
---
You received this message because you are subscribed to the Google Groups "phonegap" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phonegap+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Sönke Rohde

unread,
Feb 11, 2013, 4:14:24 PM2/11/13
to phon...@googlegroups.com
In my case I am using the InAppBrowser for OAuth and when the OAuth process is complete I just call inAppBrowser.close(). Should I file an enhancement request?

Thanks,
Sönke

Shazron

unread,
Feb 11, 2013, 4:19:28 PM2/11/13
to phonegap
Ah, I see now. What if the user changes their mind? I suppose the "Cancel" link on the form would change the url and you could capture that as well to close the form, etc

Yes, please file an enhancement request, and add your use case.

Sönke Rohde

unread,
Feb 11, 2013, 4:42:46 PM2/11/13
to phonegap
yep, exactly. monitoring the url changes is sufficient.
here the enhancement request: https://issues.apache.org/jira/browse/CB-2412

Shazron

unread,
Feb 26, 2013, 10:34:17 PM2/26/13
to phonegap
The reason that _self doesn't work is of course, once you refresh the current webview with another url, all your context is lost. Native code can know when these events happen of course, but not js (because of the context loss).

The best analog to loadstop would be the DOMContentLoaded event or use window.onload, and not sure about loadstart since it would be a chicken and an egg situation...


On Tue, Feb 26, 2013 at 6:05 PM, Travis Dahl <trav...@gmail.com> wrote:
+1. Playing around with an app that is mostly in web view so I was using _self but then after many hours of trying to figure out why my loadstart and loadstop events werent firing, I realized you had to use _blank for those.  I want the look of _self but the events and functionality of _blank. If that makes any sense. Phonegap rules!
Message has been deleted

Travis Dahl

unread,
Feb 27, 2013, 2:00:06 PM2/27/13
to phon...@googlegroups.com
Yes. I completely understand. _blank is nice because I could close the window if there was no connection and reopen one if connection was made again. BUT it has that navigation bar at the bottom. Just trying to point out another valid use case for having the option to show or hide. Thanks for the quick response and thanks again for all your hard work!
Reply all
Reply to author
Forward
0 new messages