[MGNLUI-4097] Selection should remain on the source node Created: 06/Dec/16 Updated: 30/May/17 Resolved: 26/May/17 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.5.5 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Hieu Nguyen Duc |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ux | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d 5h | ||
| Original Estimate: | 1d | ||
| 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: | |||||||||||||||||
| Sprint: | Saigon 96, Saigon 97 | ||||||||||||||||
| Story Points: | 2 | ||||||||||||||||
| Description |
|
It is a guideline from UX that a node should remain selected after a move attempt, cf https://jira.magnolia-cms.com/browse/MAGNOLIA-6893?focusedCommentId=135649&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-135649. This is not happening in the two scenarios described below. Given the following node structure:
|
| Comments |
| Comment by Mikaël Geljić [ 09/May/17 ] |
|
mmichel I can no longer reproduce the failing moves as of 5.5.4 QA—since availability prevents them (at least on the config app). However the selection problem is indeed present with all move operations (before, after, inside):
From the top of my head, this looks like overlapping (or optimistic) synchronization of the selection within the move-dialog workbench and that of the browser sub-app. A component might be shared within the same scope; or selection-changed events might be fired on a shared event bus? |