Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

StorageEstimate.usageDetails #1702

Closed
1 of 2 tasks
jarryd999 opened this issue Jun 11, 2019 · 1 comment
Closed
1 of 2 tasks

StorageEstimate.usageDetails #1702

jarryd999 opened this issue Jun 11, 2019 · 1 comment
Labels
Content:WebAPI For content triage purposes: This is related to WebAPI content Est:Medium Task estimated as medium (up to a day's work?) P3 Fix when opportunity arises

Comments

@jarryd999
Copy link

Request type

  • New documentation
  • Correction or update

Details

I've gone ahead and added usageDetails to the StorageEstimate top-level page but need to create a subpage for it, just as there is a subpage for StorageEstimate.quota and StorageEstimate.usage.

Spec PR: whatwg/storage#69
Explainer: https://jarryd999.github.io/quota-usage-details/
IDL: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/quota/storage_usage_details.idl

@chrisdavidmills
Copy link
Contributor

Hi @jarryd999 , thanks for adding this to the page. This is a little early for our core team to work on, given that it's not in the spec yet (although it looks like it will be soon).

Once it is, I'd be happy for you to add the necessary new pages to MDN (looks like we'd want a separate page for the StorageUsageDetails dict too). What is your MDN username? I'd be cool with giving you the ecessary permissions so youo can create these yourself.

@chrisdavidmills chrisdavidmills added Content Content:WebAPI For content triage purposes: This is related to WebAPI content Est:Medium Task estimated as medium (up to a day's work?) P3 Fix when opportunity arises labels Jun 12, 2019
@Elchi3 Elchi3 removed the Content label May 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Content:WebAPI For content triage purposes: This is related to WebAPI content Est:Medium Task estimated as medium (up to a day's work?) P3 Fix when opportunity arises
Projects
None yet
Development

No branches or pull requests

3 participants