InputBox currently creates the input fields with Html and Xml class and mediawiki-ui. It should use OOUI, instead.
|Open||None||T49145 Formally deprecate jQuery UI after we've stopped using jQuery UI in extensions and core (replacing it with OOUI).|
|Open||None||T100270 Replace use of jQuery UI and MW UI with OOUI across all Wikimedia-deployed extensions and core|
|Open||None||T106948 Convert InputBox to use OOUI where possible|
|Resolved||Florian||T106949 enableOOUI() not possible for Tag extensions|
@Prtksxna I think this is quite a big task on it's own. What do you think on creating some subtasks for specific elements of inputbox and using that subtasks for creating GCI tasks out of it? That could be easier to overlook for a student (which should not be overwhelmed by to big tasks)? :)
I don't think it makes sense to convert only one of the many <inputbox> forms. Using OOUI instead of plain HTML elements doesn't really improve anything and the inconsistency could be jarring when forms of different type are shown on the same page.
Is this the right task to ask for a more responsive inputbox? On Minerva on small width the form forces an embedded scrolling element and on Timeless the whole page overflows because of a larger form.
Or better to put another task together?
(T15834: Inputbox uses too much formatting may be relevant too.)