Page MenuHomePhabricator

There's no easy way to configure the buttons in the enhanced toolbar
Open, MediumPublic

Description

Several buttons were removed from the editing toolbar, for example strikeout. It makes sense to have rarely-used buttons hidden by default, but there should be an easy way to get them back.

Currently there are instruction about doing it at http://usability.wikimedia.org/wiki/Toolbar_customization , but using this page requires editing JS, which is hard even for advanced users.

https://www.mediawiki.org/wiki/Extension:WikiEditor/Toolbar_customization


See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=42810 / T44810: Provide an API to modify toolbar buttons
https://bugzilla.wikimedia.org/show_bug.cgi?id=14530 / T16530: Classic edit toolbar should be more accessible for change and modification
https://bugzilla.wikimedia.org/show_bug.cgi?id=28681 T30681: Native editButtons can't be removed or reordered through r86603

Details

Reference
bz23624

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:09 PM
bzimport added a project: WikiEditor.
bzimport set Reference to bz23624.
bzimport added a subscriber: Unknown Object (MLST).

Did you see the customizations library linked from the top? It's kinda incomplete right now, I guess; if you're missing things, you can request them on the talk page and I'll add them.

http://usability.wikimedia.org/wiki/Toolbar_customization/Library

I saw it, but most people don't want to edit JS files.

I imagine a tab in preferences, where the user can check which buttons he wants to see in the toolbar.

In the toolbar itself you can put a link called "customize", which leads to that page. (In desktop applications with rich toolbars such as Firefox or OpenOffice it is usually done by right-clicking, but this is not common in websites.)

(In reply to comment #2)

I saw it, but most people don't want to edit JS files.

I imagine a tab in preferences, where the user can check which buttons he wants
to see in the toolbar.

You could implement these extra buttons as gadgets very easily.

Yes, but they shouldn't be done as gadgets. Gadgets are usually implemented separately in every project. This looks like something that is basically useful for everyone. In English, Russian and Hebrew people complained about the disappeared strikeout button, for example.

(In reply to comment #4)

Yes, but they shouldn't be done as gadgets. Gadgets are usually implemented
separately in every project. This looks like something that is basically useful
for everyone. In English, Russian and Hebrew people complained about the
disappeared strikeout button, for example.

Could implement a few popular ones as preferences I guess.

*Mass-change: Move WikiEditor bugs to component and remove blocker bug where*