Override onBackPressed() in your Activity (Suggested)
@Overridepublicvoid onBackPressed() {
if (!webViewSuite.goBackIfPossible()) super.onBackPressed();
}
Advanced Usage
Load URL Programmatically
webViewSuite.startLoading(myURL);
You don't need to worry about WebView not being inflated here.
If WebView is not yet inflated, myURL will be loaded automatically after WebView is inflated.
myProgressBar will automatically change visibility with page loads.
I want to bind a refresh button to the WebView
webViewSuite.refresh()
Customizing WebViewClient
This is needed if you need to add more behavior to the WebViewClient.
The most common use-case is to override more URLs according to your project needs.
webViewSuite.customizeClient(newWebViewSuite.WebViewSuiteCallback() {
@OverridepublicvoidonPageStarted(WebViewview, Stringurl, Bitmapfavicon) {
//Do your own stuffs. These will be executed after default onPageStarted().
}
@OverridepublicvoidonPageFinished(WebViewview, Stringurl) {
//Do your own stuffs. These will be executed after default onPageFinished().
}
@OverridepublicbooleanshouldOverrideUrlLoading(WebViewview, Stringurl) {
//Override those URLs you need and return true.//Return false if you don't need to override that URL.
}
});
Customizing WebView Settings
WebView has a bunch of settings.
If you need to change some of them, DO NOT call getWebView() and change its settings directly. This is because webView may not yet been inflated.
Instead, use the below callback:
webViewSuite.interfereWebViewSetup(newWebViewSuite.WebViewSetupInterference() {
@OverridepublicvoidinterfereWebViewSetup(WebViewwebView) {
WebSettings webSettings = webView.getSettings();
//Change your WebView settings here
}
});
}
Loading static HTML data
Instead of startLoading(), use startLoadData() instead:
PDF files are opened using simply an ACTION_VIEW intent with the PDF URL.
And it depends, sometimes it may be weird if you go back to the WebView after pressing back button while viewing the PDF file (e.g. The PDF file was the first page, thus when you back, you simply see a blank WebView)
Since Android 5.0, the first time inflation of a WebView is very slow.
If you do not delay its inflation, It will freeze the user when user is trying to open an Activity that has a WebView. See this post for more information.
By using ViewStub with Handler.postDelayed(), the WebView is inflated after the Activity is completely created and visible to user. So when the WebView is inflating, what user sees is a created Activity with running progressbar. It perfectly looks like the time needed for the inflation of WebView is just the time needed to load that webpage.
This trick greatly improved user experience.
Actually, such trick is not only applicable to WebView, but applicable to all View elements that delays Activity creation due to slow inflation.
You can use your own Theme for FinestWebView. If you want to use pre-defined theme, use android:theme="@style/FinestWebViewTheme" or android:theme="@style/FinestWebViewTheme.Fullscreen"
Builder(@NonNullActivity activity);
// If you use context instead of activity, FinestWebView enter animation won't work
Builder(@NonNullContext context);
Status bar color will be set as colorPrimaryDark of FinestWebViewActivity's theme. Toolbar color will be set as colorPrimary of FinestWebViewActivity's theme. But, you can override theses settings using builder option statusBarColor, statusBarColorRes, toolbarColor, toolbarColorRes.
Disable Toolbar Collapsing
newFinestWebView.Builder(activity)
.toolbarScrollFlags(0) // By sending as 0, toolbar collapsing will be disabled
.show(url);
Collapsing Toolbar vs WebView BuiltInZoomControls
If you enable BuiltInZoomControls webViewBuiltInZoomControls(true), it will automatically disable toolbar collapsing.
You can force WebView to show in desktop mode by setting webViewUserAgentString("Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/20100101 Firefox/4.0").
