Created attachment 238349 [details]
reproduce the issue
Steps to Reproduce:
1. Load the attached HTML file to localhost server or http://dev.yathit.com/ydn-db/test/issues/issue-github-20.html
2. Open the file in Safari 7.1 which has indexedDB
3. You will see NotFoundError: DOM IDBDatabase Exception 8:
4. Verify that it is working in Chrome or Firefox
5. Change as suggested in line number 24, from multiple stores to single store.
6. Verify it work in Safari.
Has this been acknowledged yet? According to the specs a transaction should be able to interact with multiple object stores. http://www.w3.org/TR/IndexedDB/#dfn-scope
Safari 8.0.2 still exhibits this problem.
I hit this bug in existing code that I've been running in Chrome without problem for a couple of years. Been waiting to port it to Safari... just tried.. no go as is due to this bug.
Any movement on this? Is more information needed? This seems like it would break a large number of web apps, and is more problematic than having no IndexedDB support at all.
This is a major bug making IndexedDB unusable for any non-trivial use-case. Please fix.
The bug is still present in Safari 9.0.2, reproducible with the test case.
However! Good news!
As of WebKit Nightly r194890 (roughly 2016-01-12), I cannot reproduce this issue with the provided test case.
(In reply to comment #7)
> The bug is still present in Safari 9.0.2, reproducible with the test case.
> However! Good news!
> As of WebKit Nightly r194890 (roughly 2016-01-12), I cannot reproduce this
> issue with the provided test case.
That's actually really surprising, assuming you launched Safari using the WebKit nightly and tried it in-browser.
This is because the work for Modern IDB has been WebKit1 only so far, while Safari uses WebKit2.
BUT, if you're developing a WebKit app that uses WebKit1, and use it against the WebKit nightly, that would explain why it works.
Anyways, I'm closing this bug as a dupe of the Modern IDB bug.
*** This bug has been marked as a duplicate of bug 149117 ***