[ https://issues.apache.org/jira/browse/CB-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105484#comment-15105484 ]
Markus Kristo commented on CB-10306: ------------------------------------ I agree that this would be awesome if it could be implemented. Another benefit of using the same browser engine is that the main webview and the inappbrowser would share cookies/sessions. This is very handy for the case when you use the inappbrowser for SSO. In previous projects we have hackishly used either Ludei WebView+ or Crosswalk by doing like [this|https://github.com/mkristo/cordova-plugin-inappbrowser/commit/8949dfabd91bcef338dd3f5f9a78a188dd492b02]. That solution works, but it would be nice if the inappbrowser would support this out-of-the-box. Thanks! > [Android] Support Crosswalk or other engines through a pluggable mechanism > -------------------------------------------------------------------------- > > Key: CB-10306 > URL: https://issues.apache.org/jira/browse/CB-10306 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugin InAppBrowser > Reporter: Daniel Vicory > Labels: triaged > > Currently InAppBrowser uses the system WebView on Android, which is not > awesome for several reasons. > # WebView is only Chromium in 4.4 and up, and 4.4 uses an old one at that. > # Some features are turned off even in Chromium-based WebViews. > # WebView pre-4.4 is pretty awful and doesn't support many modern web > technologies. > I propose that it be made possible to use Crosswalk or other engines with > InAppBrowser. We have already begun work on this [on a > fork|https://github.com/appfolio/cordova-plugin-inappbrowser/tree/crosswalkSupport] > and would be willing to try to get this merged upstream. This is for Android > only though; right now we're not planning to apply these same ideas to iOS. > The general strategy we took was to reuse Cordova: it re-creates a whole > Cordova view. This makes many of the settings that were set manually no > longer necessary, as Cordova sets them by default. By default, it doesn't > reuse any of the plugins or preferences you've defined in {{config.xml}}, but > adds an "internal" plugin that the new Cordova view uses which disables > bridge access and re-implements the same functionality InAppBrowser > previously had. > To change the engine/views/etc being used, you can override > {{InAppBrowserDriver}}, which can be configured with the > {{inAppBrowserDriver}} preference in {{config.xml}}. We can open source a > driver that enables Crosswalk with this new architecture. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org