[MGNLUI-3752] In-line edited property is not always selected after saving changes Created: 19/Jan/16 Updated: 21/Mar/16 Resolved: 18/Mar/16 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.4.4 |
| Fix Version/s: | 5.4.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andreas Weder | Assignee: | Ngoc Nguyenthanh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | is-time-consuming, pain-point, ux, working-with-items | ||
| Remaining Estimate: | 0.75d | ||
| Time Spent: | 4.25d | ||
| Original Estimate: | 5d | ||
| Environment: |
5.4.4 EE Pro in Firefox 43.0.4 and Safari 9.0.2 on Mac OS X 10.11.2. |
||
| Attachments: |
|
||||||||||||||||
| 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)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | UX pain points 2018 | ||||||||||||||||
| Sprint: | Saigon 35 | ||||||||||||||||
| Story Points: | 8 | ||||||||||||||||
| Description |
|
This should have been fixed by To reproduce:
Acceptance criteria:
|
| Comments |
| Comment by Andreas Weder [ 20/Jan/16 ] |
|
Raised this to critical as it's one big topic with |
| Comment by Federico Grilli [ 27/Jan/16 ] |
|
Unfortunately I wasn't able to pinpoint the cause for this behaviour in the allowed timeframe. Admittedly though, I only looked at the server-side part of this. The "odd" thing about the issue is that the same action is used both for saving nodes (which keep selection after being edited) and properties (which lose selection). The action is info.magnolia.ui.contentapp.browser.action.SaveItemPropertyAction.execute() and the main difference there seems to be that in the node case the method returns right after saving, whereas in the property case a SelectionChangedEvent is triggered . However, even commenting out the event triggering part didn't help. Also forcing the selection of the item after the saving operation went through successfully did not work. |
| Comment by Ngoc Nguyenthanh [ 10/Mar/16 ] |
What happened?
What's solution?
Actions
|