- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 06 Jul 2020 04:34:15 -0700
- To: whatwg/storage <storage@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 July 2020 11:34:27 UTC
1: > Instead user agents should offer users the ability to clear all storage for each group of schemelessly same site origins. 2: > The storage quota of a storage shelf is a conservative estimate of the total amount of bytes it can hold. This amount should be less than the total available storage space on the device to give users some wiggle room. I guess I could add implementation-defined to that. 3: Firefox currently has this restriction, but we are thinking of removing it. As quotas are implementation-defined as per 2, I don't think we would be really disallowing anything. We're just not putting specific solutions in the specification that might not be ideal. 4: Does it matter if implementers agree it's a bad model? Exhaustively testing this across all APIs feels like a waste of time if we all want to move past it. 5: How is requiring particular UI user-friendly? I'm not sure we even know what the best UI would be here in our future partitioned world. 6: Unless we define the cost of each operation exactly we're not going to get interoperability, so I'd rather have it be somewhat vague as I'm not sure we want to commit on how to serialize code units and such. -- 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/95#issuecomment-654178974
Received on Monday, 6 July 2020 11:34:27 UTC