kaigou: this is what I do, darling (Default)
锴 angry fishtrap 狗 ([personal profile] kaigou) wrote in [site community profile] dw_suggestions2009-10-03 10:13 am

comment unscreening

Title:
comment unscreening

Area:
comments

Summary:
When unscreening a comment, instead of "your comment has been unscreened" confirm page, just go back to the unscreened comment.

Description:
Currently, to unscreen a comment, I click on "unscreen" and then I go to a brand-new page that asks me if I really want to unscreen. When I say yes, then I get another page that says "now the comment is unscreened" -- and then I have to go back multiple clicks to get back to the post where I'd unscreened the comment.

Either just send me back to the post (preferably the comment itself) when it's successfully unscreened

OR

Don't make me leave the page in the first place: I click on unscreen, and let Ajax unscreen the comment in-page.

What has me particularly confused (and is part of the usability issue for this) is that this behavior isn't consistent, and it's not obvious where it differs. On many comments, I can screen (or freeze), and the post's meta changes to reflect that (and in some styles, the post itself changes visually as well) -- then I can unscreen or unfreeze, and go back and forth without ever leaving the page.

But then, *sometimes*, I must go to a separate page to confirm, and there's the hassle, doubly so because it's unexpected because it breaks with the behavior I've been taught (by the same link, previously) is expected behavior.

Poll #1415 comment unscreening
Open to: Registered Users, detailed results viewable to: All, participants: 29


This suggestion:

View Answers

Should be implemented as-is.
15 (51.7%)

Should be implemented with changes. (please comment)
7 (24.1%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (20.7%)

(Other: please comment)
1 (3.4%)

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)

[staff profile] denise 2017-01-14 06:17 pm (UTC)(link)

Oh, gotcha. Yeah, I'll open an issue for that.