New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 729765 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature

Blocking:
issue 729772


Participants' hotlists:
OWP-Storage-DevTools


Sign in to add a comment

[Quota] Surface per-storage-type size information in QuotaManager

Project Member Reported by dmu...@chromium.org, Jun 5 2017

Issue description

Currently the GetUsageAndQuotaForWebapps returns usage on a global level:
https://cs.chromium.org/chromium/src/storage/browser/quota/quota_manager.h?q=quotamanager&dr=CSs&l=138

(Temporary storage is everything basically, Persistent is just legacy fileapi)

Let's add information on a per-storage-type basis, as this is available internally. This can then be surfaced to DevTools and such.
 
Blocking: 729772
Cc: michaeln@chromium.org
+Michael, who can provide guidance here.
Take a look at https://bugs.chromium.org/p/chromium/issues/detail?id=725238

I think we can build upon the GetUsageAndQuotaForWebApps method to return more info about how much each quotaClient is using, see the std::vector in the callback...

  virtual void GetUsageAndQuotaForWebApps(
      const GURL& origin,
      StorageType type,
      const UsageAndQuotaCallback& callback);

  typedef base::Callback<
      void(QuotaStatusCode, int64_t /* usage */, int64_t /* quota */,
           std::vector<std::tuple<QuotaClient::ID, int64_t>>)>
      UsageAndQuotaCallback;

And devtools could directly query the SpecialStoragePolicy to determine the whether the origin is durable or unlimited (etc), we could make a public accessor to help with that.
Status: Fixed (was: Assigned)

Sign in to add a comment