Add an "are you sure?" dialog to the ban user process

[teaotter]

Title:
Add an "are you sure?" dialog to the ban user process

Area:
comments

Summary:
Right now, it is easy to hit "Ban User" unintentionally and not know it. A dialog asking if you're sure would be helpful.

Description:
Right now, "Ban user" is one of the options that appears when you hover your cursor over a user's icon. The option is right above "View Journal," which makes it easy to hit accidentally.

If you click "Ban user," the option changes to "Unban user" -- but no other changes happen on the screen. It is easy to assume you just missed the "View Journal" button and click again without noticing the dialog change.

Right now, it is way too easy to ban someone unintentionally and never find out. If the banned person is polite about the ban and leaves you alone -- you'll never know why they unfriended you and went away.

An "are you sure?" dialog would make sure you didn't leave a user banned by accident. It would only add one step to banning people, so hopefully it wouldn't impair the usefulness of the feature for people who actually want to ban someone.

I think the extra dialog would be easier than sending a notification that you've banned so-and-so, although that's another option. I just don't want to ban someone and not know about it.

Poll #12915 Add an "are you sure?" dialog to the ban user process

Open to: Registered Users, detailed results viewable to: All, participants: 81

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
69 (85.2%)

Should be implemented with changes. (please comment)
1 (1.2%)

Shouldn't be implemented.
1 (1.2%)

(I have no opinion)
10 (12.3%)

(Other: please comment)
0 (0.0%)

Comments

[azurelunatic]

I think this is as-inherited, so it could use some overhaul.

[kerravonsen]

I actually prefer the notification idea, so long as it's easy enough to un-ban someone from the information given in the notification.

[montuos]

I'd be ok with getting a notification, but I would rather have this be a two-step process. Banning someone is something I don't want to be able to do accidentally!

[pleonasm]

I did this just last week. Bad laptop trackpads. As workflow goes, a notification might be better. The hover menu is a bit tricky.

[randomling]

I quite like the notification idea too, though I think that probably an "Are you sure?" dialogue couldn't hurt either.

[kyrielle]

The notification might do, but I vastly prefer the immediate dialog. Yes, it interrupts the workflow a little, but some of us never look at our clutterbomb, I mean notification center, and also some people are touchy. If you read it hours later, the person may already be gone and offended, and you may or may not be able to explain that it wasn't intentional. And they may or may not believe you.

[montuos]

I too prefer immediate feedback. Banning someone is something I don't want to be able to do accidentally!

[arethinn]

I'm confused - "ban user" is at the bottom of the list for me and would be difficult to hit accidentally when heading for "View journal". Is this not the case for others?




That said, an "Are you sure?" is probably still a decent idea.

[teaotter]

Mine says:

arethinn
Send message
Grant access
Subscribe
Ban user
View: Journal | Profile

ETA: I had no idea this could be different. I assume it may be a skin question? I'm not really sure.

[arethinn]

Possible I suppose, but I see the same list if I hover on this page (site skin, Tropo Purple) and on my own reading page (Abstractia theme). Maybe Celerity, Gradation, or Lynx behave differently...?

[denise]

it's whether you're in the new JS beta or not, i believe.

[arethinn]

Ahhhhhhh. So this is a thing that will eventually resolve itself the same way for all users?

[montuos]

Well, actually, no, this problem won't resolve itself. The point is that you can accidentally click "Ban user" without noticing, and it's just as easy to do that by missing "Subscribe" as by missing "View Journal".

[arethinn]

I don't mean the original suggestion - I mean the differences between what users are currently seeing.

[marahmarie]

Resolved itself with the last code push, which put it to the first pic for all users now afaik.