Jarryd

Hey @annevk - I work with @inexorabletash on Chrome. We have google properties that are very interested in this, we're ready to move forward with implementation. Here's our current thinking...

@annevk - This ambiguity around the size of opaque responses should remain intact given that we include the padding in each entry in Cache Storage, and thus the `usageDetails` dictionary...

@asutherland - We do expect that, in the future, consumers will have more buckets than the default bucket. We see the proposed change as a complement to said future rather...

Based on the comments above, I would like to recap what we're thinking right now. ```webidl dictionary StorageEstimate { unsigned long long usage; unsigned long long quota; StorageUsageDetails usageDetails; };...

@domenic Comments have been addressed, PTAL. If you have no further comments, then thank you for the review!

Thanks for the review! > 1. Are other implementers on board with exposing this? There has been no public support, but also no opposition. > 2. Are there bugs filed...

@annevk I'm not seeing how #86 makes this significantly easier to define. I think we are partially aligned: I've always imagined usageDetails to show a breakdown of usage per-bucket. However,...