OK, here's some annoying crap that the Android team did to the browser. Back in Honeycomb, file:// was no longer allowed to use the WebSQL database because of security reasons. I have no idea what those security reasons are, but this is the same case all the way up to Jellybean. Therefore, we use or Storage shim instead. The problem is that we enable web storage on Cordova, which is a major problem. So, I'm trying to disable this for 3.0+ now and I'll see how that works.
So, a technical workaround because the Android team doesn't believe that Cordova should have access to WebSQL. :( On Thu, Feb 21, 2013 at 11:13 AM, Simon MacDonald <[email protected]> wrote: > There is no reason why we should do that. It seems like a 0 day bug to me. > > Simon Mac Donald > http://hi.im/simonmacdonald > > > On Thu, Feb 21, 2013 at 2:05 PM, Filip Maj <[email protected]> wrote: >> I want to say that we needed this to polyfill on some older Androids.. But >> this is speculation :s >> >> On 2/20/13 4:06 PM, "Joe Bowser" <[email protected]> wrote: >> >>>While investigating this irritating issue >>>(https://issues.apache.org/jira/browse/CB-2085), I found that when we >>>first open the database, we are using the built-in WebKit Database, >>>but once I go into child browser and go back, we start to use the >>>Storage plugin. Does anyone remember which scenarios we use our >>>Storage Plugin, and which scenarios we use the built in storage, >>>because this is unclear based on the example provided. >>> >>>Joe >>
