[MGNLUI-4523] Integrate Extended Token Field Created: 15/Sep/17 Updated: 07/Sep/18 Resolved: 06/Sep/18 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Evzen Fochr |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Date of First Response: | |||||||||||||
| Epic Link: | 6.0 requisite | ||||||||||||
| Sprint: | Kromeriz 157, Kromeriz 158, Kromeriz 159, Kromeriz 160 | ||||||||||||
| Story Points: | 5 | ||||||||||||
| Description |
|
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 The second implementation would solve the Remove issue reported in
Goals:
|
| Comments |
| Comment by Roman Kovařík [ 06/Aug/18 ] |
| Comment by Robert Šiška [ 24/Aug/18 ] |
|
reverted until |