When someone has the instruction for example to "Add existing taxonomy term", then selects the desired term from the dropdown initiated by the autocomplete bar, it is reasonable for them to think their job is done.
Indeed, "Add taxonomy term" can read as a synonym for "Create new taxonomy term", which is why the button immediately next to it is labeled "Create new taxonomy term instead" to try to avoid confusion— but it is still definitely making people think.
We can fix both these problems by getting rid of the "Add taxonomy term" button.
(This of course goes for add any entity type.)
Not sure if we have to hide the button and press it with JavaScript or if the form can live without it.
Active
3.0
User interface
… realized i was totally looking at the widget from IEF Complex Open but IEF will have the same problem when ✨ Prioritize 'add existing' in nested entity creation UX to prevent duplication. Needs work lands, and the feature may be useful independently, so updating the description and screenshot and leaving this here!