Bugzilla

> It's possible (likely) that the error is coming from website/domain which has been using all its quota.
Apparently (I didn't check myself) we don't make a distinction between "disk full" and "quota full" (same error code), and this is definitely something we should improve, if confirmed.
We probably have duplicate of this bug around (will need to check for those).
>
> Jari: could you please confirm I summarized this correctly?

The summary is correct. Based on the report, it seems like either more than usual is getting stored to `localstorage` which has a low quota limit, only about 5MB (maybe it's used as a fallback in Firefox?), or the site triggers a defect which throws the quota values off. Because we don't want to encourage sites to try to find out how much free disk space a user has, we consider the quota allocation as a "virtual disk" and don't make a site-visible distinction between the two. What's important is that the site can't use more space before cleaning up.

> It's possible (likely) that the error is coming from website/domain which has been using all its quota.
Apparently (I didn't check myself) we don't make a distinction between "disk full" and "quota full" (same error code), and this is definitely something we should improve, if confirmed.
We probably have duplicate of this bug around (will need to check for those).
>
> Jari: could you please confirm I summarized this correctly?

The summary is correct. Based on the report, it seems like either more than usual is getting stored to `localstorage` which has a low quota limit, only about 5MB (maybe it's used as a fallback?), or the site triggers a defect which throws the quota values off. Because we don't want to encourage sites to try to find out how much free disk space a user has, we consider the quota allocation as a "virtual disk" and don't make a site-visible distinction between the two. What's important is that the site can't use more space before cleaning up.