You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2013/10/24 21:04:01 UTC

[jira] [Resolved] (CB-4760) Android Quirks should be documented for WebSQL

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

Andrew Grieve resolved CB-4760.
-------------------------------

    Resolution: Fixed

> Android Quirks should be documented for WebSQL
> ----------------------------------------------
>
>                 Key: CB-4760
>                 URL: https://issues.apache.org/jira/browse/CB-4760
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android, Docs
>    Affects Versions: 2.9.0
>            Reporter: Peter
>            Assignee: Andrew Grieve
>
> Apparently the WebSQL implementation is known broken on some Android devices.
> See https://issues.apache.org/jira/browse/CB-4742?focusedCommentId=13759164&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13759164
> But the Cordova provided implementation also has some behaviours which cause mobile-spec storage.spec.18 to fail
> See CB-4742, CB-3047
> Furthermore, the advice from Cordova dev is to just avoid using the WebSQL API
> See https://issues.apache.org/jira/browse/CB-3047?focusedCommentId=13633073&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13633073
> --
> The problem is that the Storage Guide documentation (http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#Storage) currently doesn't mention any *Android Quirks* at all, so as far as user knows it should all work OK as per the API guide.
> Since (from above) there are known problems with the WebSQL API, and Cordova devs recommend to avoid using the WebSQL API, and the Cordova impl of WebSQL sometimes has unexpected behaviour, then all these should be documented as Android Quirks so the user is more aware of potential issues they will face.



--
This message was sent by Atlassian JIRA
(v6.1#6144)