[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:
Cloners
is cloned by MGNLUI-4214 Selection should remain on the source... Closed
Relates
relates to MGNLUI-4194 Generalize code for move-availability... Closed
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:

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


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

  • 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?

Generated at Mon Feb 12 09:13:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.