[
https://issues.apache.org/jira/browse/CB-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090813#comment-15090813
]
Daniel Vicory edited comment on CB-10306 at 1/9/16 10:43 PM:
-------------------------------------------------------------
Yes, I'm aware - we are already using {{cordova-plugin-crosswalk-webview}}. The
problem is InAppBrowser only uses the system WebView. Web standards support is
lacking in that, especially on older versions of Android. Our use case
necessitates using InAppBrowser sometimes but without having to struggle over
an inferior browser.
As for the other plugins that are Crosswalk for InAppBrowser, we found none
that matched the API/capabilities that this has so they were off the table.
Additionally we didn't want two InAppBrowser plugins if possible (one for
Android and this one for iOS).
was (Author: dvicory):
Yes, I'm aware - we are already using {{cordova-plugin-crosswalk-webview}}. The
problem is InAppBrowser only uses the system WebView. Web standards support is
lacking in that, especially on older versions of Android. Our use case
necessitates using InAppBrowser sometimes but without having to struggle over
an inferior browser.
> [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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
