Some of our fields (e.g. personField.tag) use autocomplete, but do so with an unintuitive UI pattern.
If you type in a fragment of text, but you don't select a choice, and you exit the field, the text fragment stays displayed. There should be:
- a visual indication that this field is in an invalid state (e.g. turn it light red, or add an X)
- any hidden value that is currently set should be cleared
For this ticket
- Fix this unintuitive pattern in personField.tag (you can see it in action when adding a relationship on the dashboard). Offer that up for review.
- While you're looking at these different .tag files, consider whether there's a way to refactor such that they all share the same underlying implementation. (E.g. they could all delegate to an autocomplete.tag.)
TRUNK-2704 for an example of confusion caused by this.)