Inplace editing consolidation A: Bug-fixing
(MGNLUI-259)
|
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | forms, user interaction |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | dialog, frontend | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: | |
| Sprint: | Iteration 2013-17, Beta 2 |
| Comments |
| Comment by Christopher Zimmermann [ 03/May/13 ] |
|
Implemented behaviour is not as expected and could be very confusing to the user, maybe resulting in them changing data on the wrong property. Problem: ie if i have two properteis - "appId" and "class", If i rename appId to ZappId - then after hitting tab I will be in inplace-editing in the value field of the class row. Recommend fixing problem or reverting to previous behaviour. |
| Comment by Mikaël Geljić [ 03/May/13 ] |
|
Reverted to previous behavior without index-based lookup for new itemId. until UUID-based container helps there (at least for JCR nodes) |