[
https://issues.apache.org/jira/browse/CB-11828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684093#comment-16684093
]
ASF subversion and git services commented on CB-11828:
------------------------------------------------------
Commit e31596f60eeb3d9a7d47844b3e0e45304530d30f in cordova-android's branch
refs/heads/master from [~brodybits]
[ https://gitbox.apache.org/repos/asf?p=cordova-android.git;h=e31596f ]
Remove obsolete check for JellyBean (GH-534) (#544)
to work properly on Android Pie
was introduced in dc0bfeb0c (CB-11828)
Resolves #534
Co-authored-by: <pradiv-ku...@users.noreply.github.com>
Co-authored-by: Christopher J. Brody <chris.br...@gmail.com>
> New NativeToJSBridge does not work on Jellybean
> ------------------------------------------------
>
> Key: CB-11828
> URL: https://issues.apache.org/jira/browse/CB-11828
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Affects Versions: Master
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Priority: Blocker
>
> Apparently this got missed after weeks of review. The new default bridge
> doesn't work on Jellybean, and since we're required to support Jellybean
> until it dips below 5%, we need to be able to keep supporting it for the
> SystemWebView. However, we have a uniquely strange situation where we just
> add bridge modes to SystemWebViews, which could cause some unpredictable
> results when choosing the right webview.
> For example, we have enumerated values for setting the mode on the JS for the
> four types of nativeToJsBridges, but they can be added at random depending on
> the circumstance.
> BTW: This only affects the master branch, and not any released versions of
> Cordova.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
