Metrics are https://www.chromestatus.com/metrics/feature/timeline/popularity/1273
Usage 0.001% until a few weeks ago when usage started spiking, but with bimodal numbers. The bimodal pattern seems similar to that seen with other APIs that were being used by analytics networks (rolling out/reverting a test), but I can't see them using this method...
We need to run an HTTPArchive search.
To clarify... all the uses were of one of those libraries. Only a few uses of mega, most are dexie or alasql.
All three fall back appropriately in the absence of the function.
I think we should go ahead and deprecate (with message) and remove.
While I understand its design may be limited, I was hoping to work on a generic local IndexedDB browsing tool (beyond that in say DevTools).
Is any replacement planned to overcome the ascribed design flaws?
I've done an utility that uses NWJS so also Chromium.
The utility uses IndexedDB as database to store information. The user when the application starts can select between different databases that can create with the program (simply all databases that start with a prefix), here the use of webkitetDatabaseNames is opportune.
Is totally necessary remove that api?
Is any alternative?
Comment 1 by dtapu...@chromium.org
, Feb 27 2017