IndexedDB 2.0 In https://bugs.webkit.org/show_bug.cgi?id=149117 we've gotten a very solid implementation of IndexedDB v1 (https://www.w3.org/TR/IndexedDB/) While there's still room to finish cleaning up the loose ends for the overall Modern IDB mechanisms in that bugzilla, this bugzilla tracks implementing new features in IndexedDB v2 (http://w3c.github.io/IndexedDB/) The way the spec is advancing, some new features are stabilizing while others are still very much in flux, with occasional new ones popping up. As sub features stabilize, we should implement them, and this bug will track doing so.
Can anyone look at 177350, this is a blocker for us. It totally breaks the usage of IDB with WebCrypto!
(In reply to Stefan Sechelmann from comment #1) > Can anyone look at 177350, this is a blocker for us. It totally breaks the > usage of IDB with WebCrypto! Since storage of crypto keys works in general and we've only seen one report of this specific issues, it's hard to prioritize this over other work right now. If you can give an example of a real world, in-production site where this works in other browsers and not WebKit-based ones that could help reprioritize.
> If you can give an example of a real world, in-production site where this > works in other browsers and not WebKit-based ones that could help > reprioritize. Let's continue this discussion in the respective issue: https://bugs.webkit.org/show_bug.cgi?id=177350
(In reply to Brady Eidson from comment #2) > Since storage of crypto keys works in general and we've only seen one report > of this specific issues, it's hard to prioritize this over other work right > now. In the light of the recent development I find "works in general" at least debatable: No auto incrementing primary keys https://bugs.webkit.org/show_bug.cgi?id=182972 No indices https://bugs.webkit.org/show_bug.cgi?id=177350 Wrong prototype chain: https://bugs.webkit.org/show_bug.cgi?id=182097 Is there anybody storing crypto keys in IndexedDB with Safari? Please step forward and speak!