Inconsistent autocomplete behaviour

[frafra]

Leaving it empty is OK (even if it is mandatory - could it be related to #130?), but if it is emptied, the last selection is kept. This also happens if the user types something incorrect.

[moovida]

This is related to #130 , yes.

I was wondering about the incorrect typing. To be honest I would find this a good thing. If the needed option is not there, it would still be possible to add it?

[frafra]

I see two possibilities when there is an invalid input:

• An error is raised, and the wrong data is not store (the user should still be warned about that)
• No error or warning is raised, and the invalid data is stored

Both options make sense to me. I would prefer the first, but a flag could be set to switch between the two behaviours.

[frafra]

I just want to add that if the form input is emptied, the last selection is kept, even if an item with an empty value is specified in tags.json, so an emptied selection should be valid technically.