Closed Bug 601155 Opened 14 years ago Closed 14 years ago

IndexedDB: Tweak wording of quota prompt

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
blocking2.0 --- beta7+

People

(Reporter: bent.mozilla, Assigned: beltzner)

Details

(Keywords: uiwanted) 

The current prompt says:

This website (%1$S) is attempting to store more than %2$S MB of data on your computer for offline use.

The security team would like more context in this prompt, making it clear that the website has already used that amount.
This needs to block beta7.
blocking2.0: --- → ?
I think that string already makes it pretty clear, actually. What's not clear is that saying "yes" here means that the website can store an unlimited amount of offline data.
blocking2.0: ? → beta7+
Keywords: uiwanted
In terms of the UX guidelines: the prompt needs to ask a specific question, and the button needs to be describing even if you don't read the question being asked by the prompt.

so for instance, incorrect:

This site would like to store data.
[Ok]

correct:

Would you like to allow this site to store data?
[Allow Storage]
I don't think the specific amounts of data already stored is relevant.  Let's just go with:

Would you like to allow (%1$S) to store data on your hard drive for offline access?
[Allow Storage]
We already have that, actually. This is the second prompt, which is when the initial storage quota is exceeded, and which allows the website to store arbitrary amounts of data.

Taking.
Assignee: bent.mozilla → beltzner
Ok, then something of the form:

Would you like to give (%1$S) additional storage on your hard drive for offline access?
[Increase Storage]

as long as it is follows the pattern of question/self describing button it will work well with the new notification system.
That's not part of the request. As stated in comment 5, this allows unlimited data storage. Alex, it's cool: I've got this :)
And the way I'm going to handle this is to mark it INVALID. The existing prompt works with the options provided (Allow, Never, Dismiss) in the doorhanger, and I think clearly indicates the impact which is that the website gets to store more information on your computer.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Every doorhanger panel that provides a statement instead of a question, and non-descriptive action buttons is going to get a bug after we ship Firefox 4.  Did these ever get subjected to a ui-review?
I don't have a horse in this race, but since this came up during the security review I want to make sure everyone is fine with this resolution.

The most pressing concern was that it wasn't clear that clicking "Allow" would allow the website to store *unlimited* amounts of information (which is like, a lot).

Choffman was also concerned that we didn't mention how much data the site currently stores (which is always 50MB when this prompt comes up).

I'm personally fine with leaving this as INVALID and keeping the current string, but I wanted to give others a chance to speak up.
Seems something like the below would more accurately reflect the nature of the request (example, not proposing specific verbiage):

Would you like to allow website (%1$S) to store a potentially unlimited amount of data on your computer.
or,

[mail.google.com] is currently using 50MB of diskspace on your computer,  is it ok for it to continue to use (more | unlimited) space?
Either way, the button then needs to specifically describe the action, like "Allow Unlimited Storage."  The user should be able to infer all information by looking at the button itself, and should not be required to read the question (although they may potentially go to that extra work).  We'll need to get that fixed at some point in a follow up bug.
Keeping the current prompt-text and changing just the button text to what comment 13 says sounds like a good solution to me.
Filed follow up bug 614469 on the action button text.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.