Page MenuHomePhabricator

MultiselectWidget: Users don't press enter after entering, never see capsules
Open, Needs TriagePublic

Description

Test question: In a test of a graphical interface for cirrus search keywords, we had the question of how can users input multiple entries to a list of OR words in search (like Laptop OR Notebook).

We used TagMultiselectWidget (not entirely sure, but the element had the same mechanics) for this and expected people to create the following:

Current Problems: Of 5 users with decent web experience, none did what we assumed would be the "right" interaction. Most did:


This would have become

if they’d pressed Enter, but they did not.
So all searched for the word "Laptop, Notebook" or so, which could not be found.

Possible Solution: We decided to use "," instead of *Enter* but this may make only sense in the context of search.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 27 2017, 7:45 AM
Jan_Dittrich renamed this task from TagMultiselectWidget: Users don't press enter after entering, never see capsules to MultiselectWidget: Users don't press enter after entering, never see capsules.Jul 27 2017, 7:46 AM
Jan_Dittrich updated the task description. (Show Details)
Jan_Dittrich added a subscriber: gabriel-wmde.

@gabriel-wmde – did we use TagMultiselectWidget for the search field or another close relative of it?

Yes, we're extending TagMultiselectWidget for this. Our extension mostly state handling and to create a tag on blur.

To understand the use case correctly, it's a search input, where the tags are resembling search keywords? Is this interface already visible at a public URL?

>Is this interface already visible at a public URL?

No.

it's a search input, where the tags are resembling search keywords

Sort of. If we say "keywords" we usually mean special syntax like "intitle" or "OR". What was written in the UI-tags-elements were meant to be search-terms like "Laptop", "Notebook"

it's a search input, where the tags are resembling search keywords

Sort of. If we say "keywords" we usually mean special syntax like "intitle" or "OR". What was written in the UI-tags-elements were meant to be search-terms like "Laptop", "Notebook"

In this context it's meant as "AND" search terms then, right?

Out of curiousity, wondering what is the reason for making it a TagMultiselect component? What advantages are you aiming for at using this over a free text input like SearchInputWidget?

@Jan_Dittrich is it not?

I think anyone can see it on wmflabs, no?

@Volker_E go to https://tools.wmflabs.org/wmde-uca-test/core/index.php?title=Spezial:Suche&search=&fulltext=Suchen and activate advanced search in your beta feature.

Or is there a reason why this shouldn't work for everyone @gabriel-wmde ?

@Volker_E, my understanding was that it was intended to denote distinct "units" in the search that could also have arbitrary punctuation in them.

In this example perhaps they want to find something with the first quote OR the second quote.