498699 - >50MB Storage Warning does not Pop Up when >=50MB of Offline Storage is put on Browser

Status: RESOLVED INVALID

(Core :: Storage: Quota Manager, defect)

Description

[Aakash Desai [:aakashd]]

Build Id:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090608 Minefield/3.6a1pre ID:20090608122028

and

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090608 Shiretoko/3.5pre ID:20090608122057


Steps to Reproduce:
1. Go to the URL given in the bug report (campd).
2. Allow for Offline Storage to be pushed onto the browser from the site.
3. Push 75MB of offline storage onto the browser.

Actual Results:
No notification/warning of >50MB Offline Storage is being pushed onto the browser

Expected Results:
A notification/warning should appear.

Comment 1

[brunoais]

See: 1123637

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 3

[Jens Stutte [:jstutte]]

Hi Jan! The test URL is gone and we also recently touched storage limits. Is this bug still meaningful?

Comment 4

[Andrew McCreight [:mccr8]]

The link worked for me. Well, at least I clicked on it and it sort of sat there loading. I'm not sure what it is supposed to do.

Comment 5

[Jens Stutte [:jstutte]]

(In reply to Andrew McCreight [:mccr8] from comment #4)

The link worked for me. Well, at least I clicked on it and it sort of sat there loading. I'm not sure what it is supposed to do.

Hmm, I see the timeout screen and also developer tools gives me a NS_ERROR_NET_TIMEOUT here.

Comment 6

[Jan Varga [:janv]]

The 50MB limit was removed long time ago. At the time we didn't have the best-effort storage which automatically removes the least recently used origins, so we had to ask users for a permission if an origin wanted to store more than 50MB of data. I think bug 1123637 removed the warning/prompt as noted in comment 1. It seems we should just close this bug.

Comment 7

[brunoais]

I can confirm I didn't see the issue appearing again. I will continue monitoring.

Comment 8

[Jens Stutte [:jstutte]]

(In reply to brunoais from comment #7)

I can confirm I didn't see the issue appearing again. I will continue monitoring.

Thanks!