cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CB-11828) New NativeToJSBridge does not work on Jellybean
Date Fri, 09 Sep 2016 19:06:21 GMT


ASF subversion and git services commented on CB-11828:

Commit dc0bfeb0cc8228f755da8c60c80241fce745b7e5 in cordova-android's branch refs/heads/master
from [~bowserj]
[;h=dc0bfeb ]

CB-11828: Adding dirty userAgent checking to see if we're running Jellybean or not for bridge

> New NativeToJSBridge does not work on Jellybean 
> ------------------------------------------------
>                 Key: CB-11828
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message