Change 229662 had a related patch set uploaded (by Bartosz Dziewoński):
Use OOUI for 'create' form

https://gerrit.wikimedia.org/r/229662

Change 229662 abandoned by Bartosz Dziewoński:
Use OOUI for 'create' form

Reason:
I'm not planning to work on this currently, sorry.

https://gerrit.wikimedia.org/r/229662

Change 229662 restored by Prtksxna:
Use OOUI for 'create' form

https://gerrit.wikimedia.org/r/229662

@matmarex and I would like to mentor this for Google-Code-in-2017.

@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)? :)

@Prtksxna, @matmarex: Could you answer the last comment please, if you still think this could be suitable for creating Google-Code-in-2017 tasks? Thanks

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.

Change 229662 abandoned by Bartosz Dziewoński:
Use OOUI for 'create' form

https://gerrit.wikimedia.org/r/229662

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.)

Never mind, made T255499: Make input forms more responsive since OOUI can be messy.

Rename this task to target Codex instead, perhaps?