Content
View differences
Updated by Eric Schubert about 1 year ago
**As** an admin
**I want to** have full control over the search input while writing subject patterns
**so that** I can search with white spaces and decide when to start searching
**Acceptance criteria**
* If a user types any text into the input, no completion must be triggered.
* If the user types a `/`, the completion must be triggered.
* Any character between the `/` and the cursor must be used for the search term.
* If there is no matching attribute for the search give the user the option to add the written as plain text.
* If the user types a white space directly after the `/` the search and completion is cancelled.
* (background: early escape as an alternative to press `Esc` and also, search terms do never start nor end with white space, they'd be trimmed either way.)
* If the cursor is inside a token, the completion is triggered and the search term is everything from the beginning of the token til the cursor.
* If a completion is selected when the cursor is inside a token, the token gets replaced by the new token.
QA
* Known issues:
* on FF you can get "before" the ZWSP, and hence having it located in between text nodes
* this leads to unexpected clicking double click selections
* this leads to "double" arrow key navigation needed to overcome the ZWSP
* on chrome, you cannot get "before" any character (except it is the very first of the input), hence, you can use "DEL" on the first character of a token only from outside a token
* this leads to the token being repaired directly
**I want to** have full control over the search input while writing subject patterns
**so that** I can search with white spaces and decide when to start searching
**Acceptance criteria**
* If a user types any text into the input, no completion must be triggered.
* If the user types a `/`, the completion must be triggered.
* Any character between the `/` and the cursor must be used for the search term.
* If there is no matching attribute for the search give the user the option to add the written as plain text.
* If the user types a white space directly after the `/` the search and completion is cancelled.
* (background: early escape as an alternative to press `Esc` and also, search terms do never start nor end with white space, they'd be trimmed either way.)
* If the cursor is inside a token, the completion is triggered and the search term is everything from the beginning of the token til the cursor.
* If a completion is selected when the cursor is inside a token, the token gets replaced by the new token.
QA
* Known issues:
* on FF you can get "before" the ZWSP, and hence having it located in between text nodes
* this leads to unexpected clicking double click selections
* this leads to "double" arrow key navigation needed to overcome the ZWSP
* on chrome, you cannot get "before" any character (except it is the very first of the input), hence, you can use "DEL" on the first character of a token only from outside a token
* this leads to the token being repaired directly