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