[MGNLUI-2823] Link field should offer a button to select another item when fieldEditable=false Created: 24/Apr/14 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: |
| Description |
|
User needs to take extra step in order to pick another value in the link field (delete + add). Imho it is reasonable to add button that would allow to change/pick another value. |
| Comments |
| Comment by Andreas Weder [ 24/Apr/14 ] |
|
In the end, we'll have to implement two types of "editability" for these fields:
Assuming the "fieldEditable" refers to the first, I second your observation. I'm also fine with replacing the "Select" button with an edit icon to gain some extra space. We'll eventually have to rework those fields, use a "select" icon inside the field and icons for adding new values. But for now, that's a clear solution that brings advantages without requiring the user to learn a lot. Thanks. |