[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node Change By: Mikaël Geljić Fix Version/s: 5.5.5 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node Change By: Mikaël Geljić Sprint: Saigon 96 , Saigon 97 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Sang Ngo Huu updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node Change By: Sang Ngo Huu Original Estimate: 2d 1d Remaining Estimate: 2d 1d 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node Change By: Hieu Nguyen Duc Assignee: Hieu Nguyen Duc 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node Change By: Hieu Nguyen Duc Original Estimate: 2d Remaining Estimate: 2d 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node Change By: Mikaël Geljić Story Points: 2 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node Change By: Mikaël Geljić Sprint: Saigon 96 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / 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=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
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node when a move action fails
Title: Message Title Maxime Michel updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node when a move action fails Change By: Maxime Michel 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=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 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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:
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node when a move action fails
Title: Message Title Maxime Michel created an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node when a move action fails Issue Type: Improvement Assignee: Unassigned Created: 06/Dec/16 2:29 PM Labels: ux Priority: Neutral Reporter: Maxime Michel Security Level: Public It is [a guideline from UX](https://jira.magnolia-cms.com/browse/MAGNOLIA-6893?focusedCommentId=135649=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-135649) that a node should remain selected after a move attempt. This is not happening in the two scenarios described below. Given the following node structure: /node1 /node1/node2 /node2
[magnolia-dev] [JIRA] (MGNLUI-4097) Selection should remain on the source node when a move action fails
Title: Message Title Maxime Michel updated an issue Magnolia UI / MGNLUI-4097 Selection should remain on the source node when a move action fails Change By: Maxime Michel 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-135649 ) that a node should remain selected after a move attempt . 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 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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: