[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node

Mikaël Geljić updated an issue

Magnolia UI / https://jira.magnolia-cms.com/browse/MGNLUI-4097 MGNLUI-4097

Selection should remain on the source node

Maxime Michel 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):

- select /node2

- open the move dialog, select /node1, and hit move before

- => /node1 is incorrectly selected.

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?

Change By:
Mikaël Geljić

Summary:
Selection should remain on the source node when a move action fails

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:
* /node1
* * / node1/ node2
* /node2

# try to move /node1/node2 before or after /node2, the selection will be on /node2 (MAGNOLIA-6893)
# try to move /node2 inside /node1, the selected item will be /node1

https://jira.magnolia-cms.com/browse/MGNLUI-4097#add-comment
Add Comment

This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)

----------

----------------------------------------------------------------

For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html

Alternatively, use our forums: http://forum.magnolia-cms.com/

To unsubscribe, E-mail to: <[email protected]>

----------------------------------------------------------------