We use Vaadin TokenField in content tagging today. There's another independent implementation called Extended Token Field. Compare the two fields. Are there benefits that would justify switching to the newer implementation?

https://vaadin.com/directory#!addon/tokenfield
https://vaadin.com/directory#!addon/extended-token-field

The second implementation would solve the Remove issue reported in CONTTAGS-29:

It's too easy to remove tags by mistake because clicking anywhere in the tag removes it. Remove a tag only when the x mark is clicked.

Goals:

• Validate Vaadin 8 usage with newer APIs (& V7 compatibility)
• Consider also that we may want to make the token field a generic Magnolia field. Just like Multivalue and Twin-column, the token field can be used to link the current content item to almost any other items. It is not limited to tags. There's a really nice demo for adding multiple contacts from an address book. The user experience is superior to our current click-intensive link fields.