646781 - When asking the user for confirmation when deleting a collection, there should be two choices, "yes" and "no"

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Collections, enhancement, P5)

Description

[Nicolas Hoizey]

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: 

When deleting a collection, there are two UX issues:

- the label of current button should be a text outside the button, and the button, if left alone, should be labeled "yes" or "confirm"
- there should be two buttons, one labeled "yes" or "confirm", and the other labeled "no", "abort" or "cancel"

Reproducible: Always

Steps to Reproduce:
1. go into a collection
2. ask to delete it
3. see
Actual Results:  
one single button labeled with a question instead of an action/verb

Expected Results:  
one question, two buttons

Comment 1

[Nicolas Hoizey]

Screenshots and enhancement proposal (in french): http://gasteroprod.com/blog/quand-mozilla-pose-une-question-a-son-utilisateur-ce-n-est-pas-pour-qu-il-fasse-un-choix.html

Comment 2

[Wil Clouser [:clouserw]]

Sounds reasonable to me, although the red/green is jarring.  Chowse is our UX expert.

Comment 3

[Chris Howse [:chowse]]

(In reply to comment #2)
> Sounds reasonable to me, although the red/green is jarring.  Chowse is our UX
> expert.

I agree the button shouldn't be a question, and I like using a red button to reinforce the severity of the action. If I could suggest a few other things:

1. Rather than use 'OK'/'Cancel', how about "Delete"/"Don't Delete", or 
   something similar? This way, the buttons explicity describe the action
   they'll have, rather than forcing them to read the supporting text (and who
   reads that anyway?)

2. Show this message is a pop-up on the same page, rather than a separate one.
   It's already annoying enough to confirm actions, let alone having to WAIT
   to confirm them.

3. Lose the confirmation altogether: "delete" the collection immediately, but
   on the following page, include an option to "undo" the deletion. This 
   avoids a confirmation when unwanted, but provides away to rectify accidental
   deletions. Behind the scenes, a collection could simply be 'marked' deleted
   and excluded from listings, and then deleted permanently at a regular
   interval.

4. Install OS X's Time Machine feature on AMO, so users can review the entire 
   creation, deletion, and revision history of their collections.
   OK, maybe not...

I think we should definitely do (1). Time permitting, (2) would be nice. (3) is more of a future feature.

I'll attach an quick example of (1) and (2).

Comment 4

[Chris Howse [:chowse]]

Attachment: Delete Collection Confirmation