Change Details

**Motivation** Tests have shown that the currently used OOUI tag widget does not work well in the search use case. Although they have a very pleasing design, and make it clear where a search term starts and ends, users have difficulties understanding how to create them. Intuitively, most users used a comma to seperate search terms when searching. Therefore for now, we will implement the visually less pleasing, but better understandable alternative as described below, at the same time looking for a solution that combines the best aspects of both worlds. **Task** Make all appropriate parts of our search form react to commas as input seperators. TODO MOCK **Acceptance Criteria** - The search boxes have "usage hints" as shown in the mock. - When the user enters one of the search fields where multiple inputs are allowed, an info message appears on how to use the field (see mock). The message is the same for all appropriate search fields - When the user clicks "Search", all commas are considered input seperators - When the user expands the search bar again, all items are again separated by comma

**Motivation** Tests have shown that the currently used OOjs UI tag widget does not work well in the search use case. Although they have a very pleasing design, and make it clear where a search term starts and ends, users have difficulties understanding how to create them. Intuitively, most users used a comma to separate search terms when searching. Therefore for now, we will implement the visually less pleasing, but better understandable alternative as described below, at the same time looking for a solution that combines the best aspects of both worlds. **Task** Make all appropriate parts of our search form react to commas as input separators. **Acceptance Criteria** - The search boxes have "usage hints" as shown in the mock. - Search fields where multiple inputs are allowed, display a placeholder text that describes the field's usage regarding separating search terms (see mock). The message is the same for all appropriate search fields - Pasted content is automatically separated by commas - When the user clicks "Search", all commas are considered input separators - When the user expands the search bar again, all items are again separated by comma

**Motivation** Tests have shown that the currently used OOjs UI tag widget does not work well in the search use case. Although they have a very pleasing design, and make it clear where a search term starts and ends, users have difficulties understanding how to create them. Intuitively, most users used a comma to sepeseparate search terms when searching. Therefore for now, we will implement the visually less pleasing, but better understandable alternative as described below, at the same time looking for a solution that combines the best aspects of both worlds. **Task** Make all appropriate parts of our search form react to commas as input sepeseparators. TODO MOCK **Acceptance Criteria** - The search boxes have "usage hints" as shown in the mock. - When the user enters one of the s- Search fields where multiple inputs are allowed, an info message appears on how to use the fielddisplay a placeholder text that describes the field's usage regarding separating search terms (see mock). The message is the same for all appropriate search fields - Pasted content is automatically separated by commas - When the user clicks "Search", all commas are considered input sepeseparators - When the user expands the search bar again, all items are again separated by comma