Page MenuHomePhabricator

Lookup: clearing strategy of initial value
Open, Needs TriagePublic

Description

during usability studies we observed that when a lookup field is pre-filled, it's not immediately clear to editors that the initial value is something that has been pre-selected from a defined list of values. the issue seems to be related by the visual appearance of text in a lookup, which looks exactly like text in a text input component.

when editors try to edit this field, the experience is similar to editing text in a text field, but as soon as you remove one character from the text in the lookup, that entry becomes immediately invalid because it has been not selected from the menu.

Event Timeline

CCiufo-WMF added subscribers: bmartinezcalvo, CCiufo-WMF.

@bmartinezcalvo are you also providing feedback on this like you are for T362650?

when editors try to edit this field, the experience is similar to editing text in a text field, but as soon as you remove one character from the text in the lookup, that entry becomes immediately invalid because it has been not selected from the menu.

@AAlhazwani-WMF I don't really understand why the entry becomes invalid when the user removes one or more characters from the Lookup. At the moment, the Lookup in Codex keeps the Menu displayed when you remove characters from the Lookup input, and the menu option previously included in the Lookup keeps visible.

Grabaciondepantalla2024-04-29alas14.29.44-ezgif.com-video-to-gif-converter.gif (244×600 px, 260 KB)

Do you mean the Field becomes an error when the user starts removing characters from the Lookup? Could you provide any additional resource to clarify this?

I'm not sure if this task T363515: Include error state in Combobox, Lookup, and Radio components could solve this issue, but definitely if the Lookup itself provides an error to accompany the Field's error, it could help.