Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
storagemanager-estimate and estimate-indexeddb are more or less the same tests, the latter having been ported from the former to use `async`/`await`. The former probably should have been deleted when the latter was introduced. Since some of the tests are related to IndexedDB and some are not, this change keeps the IndexedDB tests in the file called `estimate-indexeddb` and keeps the basic tests in `storagemanager-estimate` (with minor updates). One wrinkle from the Chromium side is that the behavior of `storageManager.estimate()` is not actually specced, and as the Chromium implementation uses LevelDB, which behaves in mysterious ways, adding things to the database does NOT always increase the reported usage size. Both of these tests operate on large things, which typically do increase usage, however we noticed that for one reason or another, the test that adds an *uninitialized* ArrayBuffer starts failing on Windows if durability is set to relaxed. There are other ways to make the test fail as well: using a shorter name for the database, or putting small values, does not reliably increase the reported usage. This is all fine in the sense that it isn't defined behavior, but it does suggest that working in this area or on tests of this ilk is a bit of a minefield. These tests probably should not exist as WPT, at least not until quota behavior is specced (see whatwg/storage#110). But it would also be sort of a shame to delete WPT that are passing, so I've left them in place for now. Bug: 1489517 Change-Id: I6619f504ce92e428054691ac6bf54a0e14e3ce5f
- Loading branch information