-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggest inappbrowser open as hidden #139
Comments
Thanks for the suggestion. I'll take it into consideration :-) |
That is a very common issue. When network is "floating" between online and offline states, you can end up having a NET::ERR_CONNECTION_TIMED_OUT or other similar error tossed out of inAppBrowser How would loadstop catch such an error and get the user back to the app? |
Its more of a dirty trick to keep the flow through the browser from getting stuck. If the connection does not come to life you end up closing the inappbrowser with a timer, if the connection is good then you show it. Once it is shown you could still have other network issues but at least you know you got to Facebook to begin with.
|
Did not see your answer, but I have done it thru a different approach (without timeout). I will make a commit on my repo. |
…aded page if error occurs, never show it nraboy#139
Pull requests are always encouraged if you want to contribute to this project. |
…ginal function set on addEventListener See https://issues.apache.org/jira/browse/CB-4819 extracted functions used for events so that removeEventListener would work as expected Original issue: nraboy#139
…ginal function set on addEventListener See https://issues.apache.org/jira/browse/CB-4819 extracted functions used for events so that removeEventListener would work as expected Original issue: nraboy#139
What happened to this? can it be used somehow? any docs? |
I don't believe @ffabreti ever made me a PR. |
Perhaps open the inappbrowser as hidden and look for the loadstop event to show. Many times the web page will not load because the site is down or not available, worse the network connection is down. This causes the app to hang to the user because the inappbrowser is blank. $timeout is needed to kill the browser if this happens.
The text was updated successfully, but these errors were encountered: