This is a known issue on Storage API v1 and planned to be handled on v2, IIRC. The reason for the implementation part is the same as Andrew mentioned in comment #2. The reason for UX part was that "are users aware of persisted storage would be removed once the permission is clear". For instance, if a user goes the about:preference and remove all existing permission, would they expect all the persisted storage will be removed? At that time, we were not so sure users can bundle these two things together, so we didn't take care of that on v1. BTW, because persisted storage might have occupied more than group limit, we might need to consider if we just want to remove as a little storge as possible to fix the quota or just remove all the persisted storage. We could just remove the whole the persisted storages once permission is clear if we want to make it simple, though.
Bug 1558478 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is a known issue on Storage API v1 and planned to be handled on v2, IIRC. TThe implementation is the same as Andrew mentioned in comment #2. The reason for UX was that "are users aware of persisted storage would be removed once the permission is clear". For instance, if a user goes the about:preference and remove all existing permission, would they expect all the persisted storage will be removed? At that time, we were not so sure users can bundle these two things together, so we didn't take care of that on v1. BTW, because persisted storage might have occupied more than group limit, we might need to consider if we just want to remove as a little storge as possible to fix the quota or just remove all the persisted storage. We could just remove the whole the persisted storages once permission is clear if we want to make it simple, though.
This is a known issue on Storage API v1 and planned to be handled on v2, IIRC. The implementation is the same as Andrew mentioned in comment #2. The reason for UX was that "are users aware of persisted storage would be removed once the permission is clear". For instance, if a user goes the about:preference and remove all existing permission, would they expect all the persisted storage will be removed? At that time, we were not so sure users can bundle these two things together, so we didn't take care of that on v1. BTW, because persisted storage might have occupied more than group limit, we might need to consider if we just want to remove as a little storge as possible to fix the quota or just remove all the persisted storage. We could just remove the whole the persisted storages once permission is clear if we want to make it simple, though.