Query on implementation status

[SubhamoyS]

Hello,

I am trying to understand the utility and/or importance of implementing kv-storage for Firefox. It has been some time since the intent to prototype and I would love to know if this is still being actively pursued in the Chromium project.

Thanks in advance!

[domenic]

Hi, thanks for reaching out. At this point, due to a combination of concerns over built-in modules and a shifting of the Storage team's priorities, Chromium is no longer pursuing KV Storage.

I will work on shutting down the repository to make this more clear.

[domenic]

I've removed the usage of built-in modules from this repository, and added a note saying

Work on this specification is currently suspended, as no browser teams (including the Chromium project, which originated the proposal) are currently indicating interest in implementing it.

Let me know if Mozilla is interested in taking this up, and I can change the wording. I'd be happy to give you or other Mozilla engineers access to the repository if they want to take up the project!

[asutherland]

My impression of rough consensus at TPAC suggested that the plan would be to try and fold the API design of KV-storage into IndexedDB as its long-desired promise-based API, so I think the work might just happen there? (Not that such a thing would happen immediately.)

[annevk]

cc @inexorabletash