Re: [w3c/IndexedDB] API to enumerate databases (#31)

> I've never seen any use case for webkitGetDatabaseNames except for a browser plugin (e.g. the PouchDB Inspector). In terms of consistency guarantees I'd say it's not super important, since it's only needed for debugging.

**One potential use case from LinkedIn**
As we build out more PWA stuff, there's a need to build up a family of "kill switches", one of which is designed to address situations where *corrupt/unsafe data could have been stored on user agents*. Essentially we want some of the functionality described in the [`Clear-Site-Data`](https://w3c.github.io/webappsec-clear-site-data/) proposal.

There's a very real possibility that teams may have widely varying database names, and it's helpful to be able to wipe out any potentially harmful data across ALL databases (and AFAIK there's no path forward without the ability to enumerate over db names).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/31#issuecomment-324756055