[ https://issues.apache.org/jira/browse/CB-12218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser resolved CB-12218. ----------------------------- Resolution: Fixed > inconsistent null handling between EVAL and ONLINE bridge modes > --------------------------------------------------------------- > > Key: CB-12218 > URL: https://issues.apache.org/jira/browse/CB-12218 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android > Affects Versions: 6.0.0 > Environment: Android > Reporter: Alan Kinzie > Assignee: Joe Bowser > Attachments: CB12218.zip > > > If the Android native code invokes the success callback like this: > callbackContext.success(null); > then the value given to the javascript callback changes depending on the > bridge type used. > If the ONLINE_EVENT type is used, then null will be passed to the javascript > callback. > ie: if result is the parameter of the javascript success callback then > result === null // will be true > result === "" // will be false > If the EVAL_BRIDGE type is used, then an empty string will be passed to the > javascript callback. > ie: if result is the parameter of the javascript success callback then > result === null // will be false > result === "" // will be true > The value of the parameter given to the success callback should not change > depending on the bridge type. Since ONLINE_EVENT was the default before > cordova android 6.0.0, I am inclined to think the ONLINE bridge is doing the > correct behaviour. Also, converting null to an empty string loses > information. Therefore I think the EVAL mode should to be changed to be > consistent with the ONLINE mode. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org