[
https://issues.apache.org/jira/browse/CB-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160253#comment-13160253
]
Simon MacDonald commented on CB-97:
-----------------------------------
Well, it is a difference in implementation between Android and BB. However, the
getInfo method should really be considered a private function. The Connection
class uses the getInfo function to update it's type property. The best, and
easiest way to check the connection state is to just interrogate:
if (navigator.network.connection.type == "none") {
alert("no connection");
} else {
alert("connection!");
}
Each time the native side determines there is a change in a connection type it
calls getInfo as it's success callback.
> navigator.network.connection.getInfo returns wrong parameter to callback
> ------------------------------------------------------------------------
>
> Key: CB-97
> URL: https://issues.apache.org/jira/browse/CB-97
> Project: Apache Callback
> Issue Type: Bug
> Components: BlackBerry
> Reporter: Michael Brooks
>
> The blackberry implementation returns a JSON object to the getInfo success
> callback.
> Android, for example, returns just a string.
> Which one is the right one? I can't tell from the callback-test repo.
> Here's an example of a problem I have currently on an Android and BlackBerry
> callback project:
> {code}
> navigator.network.connection.getInfo(
> function(type)
> {
> if(type == "none" || (typeof type.type != 'undefined' &&
> type.type == 'none'))
> {
> alert('no connection');
> }
> else
> {
> alert('connectioN!');
> }
> },
> function()
> {
> alert('something bad happened');
> });
> {code}
> So the getInfo callback, in Android case, compares to a string; BlackBerry
> has to check it's an object and look at one of the object properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
