This feature is only shown in the feature list to users with edit access.

We propose to remove support for the legacy storage quota API, window.webkitStorageInfo in 1st+3rd party contexts. The overall process started with a deprecation warning upon any method calls. This deprecation phase started in 2013, and following the recent usage number plus analyses on the type of usage the next action will be in a pre-phase, to disable the API with an exception thrown at every method call. And, after a given mitigation period get rid of the code within the window object.


A number of storage APIs (including quota-managed storage APIs) will be partitioned in third-party contexts. The API window.webkitStorageInfo is Chrome-only, and has been deprecated since 2013. Rather than investing more support on these legacy API we propose to disable it in 1st and 3rd party contexts.


Specification link

Specification being incubated in a Community Group

Status in Chromium


No active development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals


Search tags

legacy, quota, storage,

Last updated on 2022-01-18