Bug 160306 - IndexedDB 2.0
Summary: IndexedDB 2.0
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 161414 165215 165928 177350 160352 163749 163805 163910 163927 163954 164097 164294 164332 164359 164383 164403 164404 164405 164406 164416 164424 164466 164504 164528 164566 164602 164641 164754 164932 164974 165000 165166 165186 165216 165221 165242 165256 165257 165267 165330 165430 165634 165802 165816 165912 165929 165956 165978 166014 166984 167576 182972
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-28 11:26 PDT by Brady Eidson
Modified: 2018-02-24 04:41 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brady Eidson 2016-07-28 11:26:15 PDT
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.
Comment 1 Stefan Sechelmann 2018-01-21 13:10:00 PST
Can anyone look at 177350, this is a blocker for us. It totally breaks the usage of IDB with WebCrypto!
Comment 2 Brady Eidson 2018-01-22 20:35:52 PST
(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.
Comment 3 Stefan Sechelmann 2018-01-23 02:58:57 PST
> 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
Comment 4 Stefan Sechelmann 2018-02-24 04:41:09 PST
(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!