persistent-storage" can be used as indic
User agents should not distinguish between network storage and site storage in their user
interface. Instead user agents should offer users the ability to remove all storage for a given
-site. This ensures that storage from one source cannot be used to revive storage from another
-source. This also helps users avoid having to know about the different ways in which sites
-can store data.
-
-This is still a concern due to HTTP ETag... - -Credentials storage should still be separated however as it might contain data the user might not be -able to revive, such as an autogenerated password. +site. This ensures to some extent that network storage cannot be used to revive +site storage. This also reduces the amount users need to know about the different ways in +which sites can store data. + + +Credentials storage should be separated as it might contain data the user might not be able to +revive, such as an autogenerated password. Since permissions storage is mostly simple booleans it +too can be separated to avoid inconveniencing the user. Credentials and permissions are also +somewhat easier to understand and differentiate from network storage and site storage.
User agents should not distinguish between network storage and site storage in their user -interface. Instead user agents should offer users the ability to remove all storage for a given site. This ensures that storage from one source cannot be used to revive storage from another -source. This also helps users avoid having to know about the different ways in which sites can store data.
-This is still a concern due to HTTP ETag...
-Credentials storage should still be separated however as it might contain data the user might not be -able to revive, such as an autogenerated password.
+interface. Instead user agents should offer users the ability to remove all storage for a given site. This ensures to some extent that network storage cannot be used to revive site storage. This also reduces the amount users need to know about the different ways in +which sites can store data. +Credentials storage should be separated as it might contain data the user might not be able to +revive, such as an autogenerated password. Since permissions storage is mostly simple booleans it +too can be separated to avoid inconveniencing the user. Credentials and permissions are also +somewhat easier to understand and differentiate from network storage and site storage.
When the user agent notices it comes under storage pressure and it cannot free up sufficient space by clearing network storage and non-persistent boxes within site storage, then the