I (and probably much others) would have a much faster workflow if I could mark already locked accounts with a CSS rule on a abuse filter log page.
Acceptance criteria
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | • TBolliger | T169461 Add locked account css class to abuse filter logs | |||
| Duplicate | None | T169839 Strikethrough blocked/locked accounts anywhere they are displayed |
Seems like this would be good for both locked and blocked accounts, right? Also, I don't see a reason this should be limited to the AbuseFilter logs. Places like edit history would also benefit from this. I imagine the best solution would be to take a gadget like markblocked and make it into a core feature behind a preference instead.
Giving much support to this. We currently use markblocked in fawiki, and it has been really helpful with CheckUser activities too. Let's make this a core feature where whenever a link to a user account is created, it is assigned a "blocked-user" class, and in the core CSS that class has some distinctive feature (e.g. italicized, or lighter color font, much like markblocked).
@Huji — Hi there. We've already sized this ticket and taken it into our sprint. I've reverted your edits because the scope of your request is much different than what is outlined just from the original task. Please create a new ticket if this one doesn't cover what you need.
@TBolliger I still believe this is best resolved upstream. I already submitted a patch for other task which takes care of this. I also posted a screenshot. Feedback on the patch is welcome.
With the changes in T172348, this issue is resolved. I gave the patch in that ticket a +1