Page MenuHomePhabricator

Confirmation prompt for rollback action (#7 2017)
Open, NormalPublic

Description

Survey: 2017

Update sites on-wiki: English, German

Insights (for details see on-wiki update pages):

  • The rollback right in most wikis is given to rollbackers and sysops. However, most people with rollback rights are in the editors user group, mainly from de- and pl-wiki.
  • Many people who were given the rollback right specifically (i.e. are part of the rollbackers group), do not want anything that increases the effort to roll sth. back
  • People who have the right among many other rights might not always use the right, and would appreciate a confirmation prompt to avoid accidental rollbacks

Development Plan:

  • Build an inline confirmation like the thanks confirmation, which appears on the diff page and on the list pages ( a patch was already started for that)
  • For people with the rollback right, make it an opt-in feature per user that can be enabled through the preferences section
  • For people with the rollback right on de-wiki, make the feature an opt-out feature

Related tasks:
T49782: Rollback workflow needs further thought: In this task is also the beforementioned patch

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 13 2018, 12:52 PM
Lea_WMDE triaged this task as Normal priority.Jul 13 2018, 12:55 PM
Lea_WMDE updated the task description. (Show Details)
JStrodt_WMDE updated the task description. (Show Details)Jul 13 2018, 1:28 PM
stjn added a subscriber: stjn.Jul 13 2018, 3:20 PM

Can’t you just do a gadget please? I seriously don’t understand why all of this development is even needed.

Jony added a subscriber: Jony.Mar 19 2019, 9:38 AM

Can’t you just do a gadget please? I seriously don’t understand why all of this development is even needed.

I suppose a full extension allows revert protection feature to work even without javascript, and in the common case of a click done by the user before the full page load with its scripts.

Izno added a subscriber: Izno.Wed, Mar 20, 11:14 PM

Can’t you just do a gadget please? I seriously don’t understand why all of this development is even needed.

Besides Framawiki, gadgets don't have the same localization mechanism nor are they as readily advertised to small wikis who may want the same functionality without the upkeep of a gadget.

stjn added a comment.Thu, Mar 21, 11:30 AM

I suppose a full extension allows revert protection feature to work even without javascript, and in the common case of a click done by the user before the full page load with its scripts.

I was asking this in July 2018 when this reasoning wasn’t originally provided, so with the addition of Noscript version I do see why it can be done this way. I am not even against this feature (moreover, I have it in my scripts), I was slightly concerned with, at the time, the feature bloat of yet another minor JS-only feature supported only by the German community.

(@Izno: Localisation can be done for gadgets, and small wikis usually just copy the code from bigger ones.)

Izno added a comment.Thu, Mar 21, 10:20 PM

I suppose a full extension allows revert protection feature to work even without javascript, and in the common case of a click done by the user before the full page load with its scripts.

(@Izno: Localisation can be done for gadgets, and small wikis usually just copy the code from bigger ones.)

You missed the point. It's that the mechanism differs significantly and even I would say preferentially. And as for copying code from bigger ones a) they shouldn't, b) T22153, c) they shouldn't need to because it should just be a feature of the core software.

Lofhi added a subscriber: Lofhi.Sat, Mar 30, 1:41 PM