Annotations: Forced keyword autocomplete makes entry of certain strings impossible #3116

Open
opened 2018-04-24 11:34:40 +00:00 by rlx · 0 comments
Owner

We may need an option to disable autocomplete, or we will have to improve the UI (like: current input field value is always present in the dropdown).

The concrete case: if the keyword "foo" already exists, it's practically impossible to enter the keyword "FOO".

We may need an option to disable autocomplete, or we will have to improve the UI (like: current input field value is always present in the dropdown). The concrete case: if the keyword "foo" already exists, it's practically impossible to enter the keyword "FOO".
rlx added the
frontend
label 2018-04-24 11:34:40 +00:00
rlx added this to the 14.04 milestone 2018-04-24 11:34:40 +00:00
0x2620 was assigned by rlx 2018-04-24 11:34:40 +00:00
rlx added the
major
defect
labels 2018-04-24 11:34:40 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: 0x2620/pandora#3116
No description provided.