Expose Webview to allow custom config/handlers

[airandfingers]

Hi, I see that you closed #33 citing that "Providing a custom UI goes against the Oauth2 spec", but there are other reasons that exposing the Webview would be very useful:

• Set Android WebView settings:
  • webview.android.setWebChromeClient(new android.webkit.WebChromeClient());
  • android.getSettings().setBuiltInZoomControls(false);
  • android.getSettings().setUserAgentString('CUSTOM_UA_STRING');
• Set custom loadStartedEvent and loadFinishedEvent handlers

Are there other ways to accomplish the tasks above without accessing the Webview?

[airandfingers]

Here's how I messily satisfied this need in the original nativescript-oauth plugin: alexziskind1/nativescript-oauth#58

[eliottrobson]

The main one for me is to be able to set the navigation button back text to the same title as the previous page.

nativescript-oauth2/src/tns-oauth-login-webview-controller.ts

Line 101 in accee37

navBtn.text = "";

@alexziskind1 Is this something you would be happy to PR if I made options configurable?

[maplepam]

May we also allow config to add an activity indicator while the Webview is still loading the content and hide on pageLoadFinished?

var myloadingObject = { isLoading: true };
var indicator = new loading_indicator_1.ActivityIndicator();
indicator.bind({
   sourceProperty: "isLoading",
   targetProperty: "busy"
}, myloadingObject);
    
var stack = new stack_layout_1.StackLayout();
var grid = new grid_layout_1.GridLayout();
grid.addChild(webView)
stack.addChild(indicator);
stack.addChild(grid);