| matmarex | |
| Jan 29 2015, 12:57 AM |
| F4539165: T87832 ComboboxInputWidget II - OOjs UI Demos 2016-09-29.png | |
| Sep 30 2016, 4:41 AM |
| F4539166: T87832 ComboboxInputWidget OOjs UI Demos 2016-09-29.png | |
| Sep 30 2016, 4:41 AM |
| F4440474: Screen Shot 2016-09-07 at 10.33.42.png | |
| Sep 7 2016, 5:38 PM |
| F174869: Screenshot 2015-05-06 20.04.28.png | |
| Jun 5 2015, 12:09 AM |
| F32711: IZpyoFO.png | |
| Jan 29 2015, 12:57 AM |
| F32714: JadU5Jq.png | |
| Jan 29 2015, 12:57 AM |
MediaWiki UI ComboBox design is needed (and by 'design', I meant both design and implementation). The current one is a bit messed up.
Current design looks thus:
I tried to cook up something better here: https://gerrit.wikimedia.org/r/#/c/186536/
Proposed:
 |  |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T87832 Redesign the ComboBox in OOjs UI's MediaWiki theme | |||
| Resolved | • Volker_E | T101533 Re-design of drop-down menu |
Change 191877 had a related patch set uploaded (by Esanders):
Fix DropdownWidget and ComboboxWidget appearance
Change 191877 abandoned by Bartosz Dziewoński:
Fix DropdownWidget and ComboboxWidget appearance
Reason:
Not being actively worked on, superseded by https://gerrit.wikimedia.org/r/#/c/210881/
Change 210881 had a related patch set uploaded (by Bartosz Dziewoński):
MediaWiki Theme: comboBoxWidget: Implement parts of new design
Change 210881 abandoned by Prtksxna:
MediaWiki Theme: comboBoxWidget: Implement parts of new design
Current L&F:
There's now just one deviation from M54 that I can see, which is that drop-down "caret" control is an icon, not a button. This has three effects:
Do we want to make that change too?
@Jdforrester-WMF From an user experience point of view it makes sense to still change the appearance of the dropdown to a button, because it must be made clear to the user that a combobox is acting as an input with an additional dropdown functionality.
Sure, there are normal input fields that might feature something like an autocomplete menu as well. In my understanding the difference would be that combobox is already featuring results before any keyboard input while latter needs to have input before a menu appears.
The demos of ComboBoxInputWidget, ComboBoxInputWidget (empty) and CapsuleMultiselectWidget currently (as of v0.17.9) seem ambiguous to me in when to use which. Related to this, ComboBoxInputWidget (empty) shouldn't feature a dropdown indicator when there is nothing to show. That contradicts user expectations.
Change 313552 had a related patch set uploaded (by VolkerE):
ComboBoxInputWidget: Align to design specification
Change 313552 merged by jenkins-bot:
ComboBoxInputWidget: Align to design specification
