IndexedDB compliance #72
Conversation
They have been deprecated. The documentation just uses strings: http:https://www.w3.org/TR/IndexedDB/#cursor-concept
Added logic to take out the parameter entirely if it was null. Reference: http:https://www.w3.org/TR/IndexedDB/#widl-IDBObjectStore-openCursor-ID
|
It looks like this breaks the checkpoint test, and everything in firefox, but the cursor constants looks like they are backwards compatible This is awesome, thanks a lot, will work on top of these patches and try and get them in, its awesome to have canary support |
|
Hmm, that's too bad about Firefox. I can't believe how quickly this stuff is changing. Chrome just came out with a new version yesterday, Firefox has a new one in a couple days, and IndexedDB's spec was just updated a week or so ago. Interesting. Anyways, syntax errors are fixed. Thanks for pointing them out. I should figure out how to use qunit. |
|
hah yeh life on the bleeding edge :P I have updated the instructions for running the test suite (@https://github.com/daleharvey/pouchdb#running-the-tests), its a little fiddly for now, until we get native CORS support in couch working, once PouchDB is at some level of stability that will be my focus I usually hang around in #couchdb if you have any questions, cheers |
Made a few changes to make it comply with the W3 IndexedDB specs. (This also fixed issues that I was getting in Chrome 21)