Page MenuHomePhabricator

Replace WikiEditor widgets with OOUI-based (VisualEditor) components
Open, Needs TriagePublic

Assigned To
Authored By
Nov 8 2018, 2:18 PM
Referenced Files
Restricted File
Jan 17 2024, 9:32 PM
"Love" token, awarded by Rail."Love" token, awarded by Iniquity.


This is not a priority for any team, but it would be good to replace current jQuery UI-based widgets in default wikitext editor (WikiEditor, WE) with OOUI-based reusable components from VisualEditor (VE) for two following reasons:

  1. Feature disparity. The interface for inserting a file is far more developed in VE in comparison with WE, search and replace interface is reportedly the same. WE users can benefit from having features like file search and autocomplete after converting to OOUI and reusing code from VE.
  2. UI standardisation. Currently WikiEditor uses both OOUI and jQuery UI: jQuery UI is being used in all widgets, OOUI is being used in the styling of buttons and in file upload interface. TemplateWizard beta feature also uses OOUI instead of jQuery UI. With jQuery UI being somewhat deprecated in usage, it would be good to remove inconsistencies.

List of components using jQuery UI:

  • Insert a link
  • Insert a file
  • Insert a reference
  • Insert a table
  • Search and replace

Not every interface, obviously, can be replicated from VE one to one.

These will be, in my opinion, pretty uncontroversial changes, as their deployment will increase usability of the editor. Maybe then something similar to T174119: Fix several design features of WikiEditor and CodeEditor to match the general style can be done, as those stylistic changes also seem to be uncontroversial after changing all icons to OOUI in T191031.

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

In T289214, the text input widgets in the link-insertion dialog will be replaced with OOUI ones. The dialog itself will stay as jQuery UI though.

Separately, it is worth noting that the jQuery UI forms began to interfere with accessibility (font size) in the monobook.