This was proposed and discussed in this thread:
Plunking this in the bug database so we can track interest/objections/alternate proposals. Discussion stalled on the thread, but continued interest has been expressed offline.
Chrome has implemented this as webkitIndexedDB.getDatabaseNames() in response to user requests; the primary uses cases are for application debugging and diagnostics for deployed web apps. Tools like the Web Inspector which provide an interactive means of exploring local IDB instances address the former use case, but not the latter.
Agreed that this can be useful. I think it shouldn't use DOMStringList, as currently there's a want to remove those in favour of Arrays :-)
It'd be interesting to be able to get some guarantees, but this proposal is very easy to implement. Has anyone any good ideas how a guaranteed getDatabaseNames() would work?
Yup. Agreed that we should definitely do this, but for v2. I think it should be totally doable to specify and implement in such a manner that it fulfills the requirements in
Filing away with the other v2 bugs.
Just for posterity, in case anyone goes looking:
Since there was no consensus to add this API, the Chrome API is currently prefixed as webkitGetDatabaseNames() - still hanging off the IDBFactory object.
Moved to https://github.com/w3c/IndexedDB/issues/31