You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Joe Bowser (JIRA)" <ji...@apache.org> on 2016/09/09 21:30:22 UTC

[jira] [Resolved] (CB-11828) New NativeToJSBridge does not work on Jellybean

     [ https://issues.apache.org/jira/browse/CB-11828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser resolved CB-11828.
-----------------------------
    Resolution: Fixed

Tested on my Samsung Galaxy Note running 4.1.2, closing.

> 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
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: 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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org