Remove the web layer, formalize mojo layer, etc.
Will probably have the largest performance benefits for IndexedDB.
Unknowns
* The amount of work to untangle task queuing
* If this should be done before or after a mojoification update: https://bugs.chromium.org/p/chromium/issues/detail?id=717798
In issue 899446, IndexedDB onion souping led to a new bug where Chrome canary+dev users could not read/write compatible IndexedDB instances with Chrome stable/beta. That issue is marked fix since master has a revert of the breaking change.
This issue will track a fix to the Mojo IDBValue.bits type to avoid that error going forward.
Comment 1 by jsb...@chromium.org
, Jun 9 2017