- From: Daniel Murphy <notifications@github.com>
- Date: Mon, 19 Aug 2019 16:35:16 -0700
- To: whatwg/storage <storage@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/storage/issues/74@github.com>
**draft** topics to talk about during the WebApps WG ## Storage Buckets ### Problem TODO Maybe something along the lines of: Developers have consistently wanted browser-supported ways of evictable storage, where it doesn't 'wake up' the website and just evicts things that the website explicitly wants evictable. Boxes allows this Also - encryption? ### Proposal Spec: TODO Tracking: TODO ## Storage Corruption ### Problem All browsers must deal with the situation where bits on disk change resulting in corruption. Currently there is no specification of what should be done in these cases leading to each browser creating ad hoc solutions. ### Proposal To improve developer confidence in the platform we should: 1. Provide a mechanism to report storage corruption in a consistent manner to sites. 2. Attempt to standardize possible browser mitigations when corruption is encountered. Spec: [Explainer in progress, aiming to have available before TPAC] Tracking: TODO ## Low Disk Space Signal API (pwnall@?) ### Problem Some operating systems exhibit stability problems when free disk space becomes dangerously low. Web applications that want to offer a good UX need to be aware when the disk space is running low, so they can avoid causing more disk space consumption. We’d like to focus on the following use cases. 1. An application with offline functionality wants to hide the ”Enable Offline” UI for users who are low on disk space. 2. An application that syncs content for offline use wants to stop syncing new content and show a warning when disk space is running low. We are aware of large Web properties that currently rely on Chrome’s quota reporting API to detect when free disk space is running low. In the future, we (the Chrome team) will change this API’s behavior, and applications will not be able to use it to detect free space. ### Proposal Spec: TODO Tracking: TODO A previously proposed approach involved waking up origins so they can reduce their disk usage, and was abandoned due to performance concerns. We would like to propose an approach that only sends low disk signals to origins with active execution contexts. ## Storage Quota Behaviors (pwnall@?) ### Problem TODO ### Proposal Spec: https://github.com/whatwg/storage Tracking: N/A We would like to explore a cross-browser consensus on standardizing more behavior around quota. We are starting by kicking off MDN documentation here that covers all browsers. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/storage/issues/74
Received on Monday, 19 August 2019 23:35:38 UTC