![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
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.
This suggestion:
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%)
no subject
no subject
(The text or icon changes to reflect whether it's screened or unscreened, even if the rest of the style doesn't.)
no subject
no subject
no subject
no subject
no subject
no subject
From what I can tell, though, if the reply is screened by the system -- like an anonymous reply or when you've got it set up to screen replies -- then it will send you to a separate page. After that, if you re-screen, it happens in-page. If the comment isn't screened or isn't frozen at first, then if you screen or freeze, it does it in-page, and if you un-screen or un-freeze, it also does it in-page. So it's just that one instance where it takes you off-page. If that helps, at all. (And I'm not sure this is always the case, but it's what I could duplicate on my own journal, at least.)
no subject
no subject
no subject
no subject
no subject
Oh, gotcha. Yeah, I'll open an issue for that.