16137 2012-02-27 18:39:11 +0000 IndexedDB: Add API for enumerating databases 2015-08-10 20:21:18 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified All All RESOLVED MOVED P2 normal --- 1 jsbell dave.null dale jonas mike odinho public-webapps public-webapps-bugzilla oldest_to_newest 64654 0 jsbell 2012-02-27 18:39:11 +0000 This was proposed and discussed in this thread: http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1528.html 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. 64660 1 odinho 2012-02-27 23:36:09 +0000 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? 64881 2 jonas 2012-03-02 04:01:30 +0000 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 http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1537.html Filing away with the other v2 bugs. 69737 3 jsbell 2012-07-09 16:04:55 +0000 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. 122544 4 jsbell 2015-08-10 20:21:18 +0000 Moved to https://github.com/w3c/IndexedDB/issues/31