Sorry for the late reply. On some platforms navigator.onLine doesn't update. I believe older Androids had this issue.
Our API is event-based which is a bit more elegant than polling a dangling property off navigator. Not sure what the latest redux for the appropriate W3C spec is. On 1/18/13 12:39 PM, "Bryan Higgins" <[email protected]> wrote: >On BlackBerry 10, there is a native implementation of navigator.onLine. >This is a more reliable test than checking connection.type. For example, >the device could be connected to BlueTooth, but WebKit has no network >connectivity. > >Is there a reason we override this for other platforms? I understand the >need to polyfill for platforms on which this isn't available. > >Thanks, >Bryan >--------------------------------------------------------------------- >This transmission (including any attachments) may contain confidential >information, privileged material (including material protected by the >solicitor-client or other applicable privileges), or constitute >non-public information. Any use of this information by anyone other than >the intended recipient is prohibited. If you have received this >transmission in error, please immediately reply to the sender and delete >this information from your system. Use, dissemination, distribution, or >reproduction of this transmission by unintended recipients is not >authorized and may be unlawful.
