[MGNLUI-4018] "Move Inside" button's state is incorrecly handled Created: 16/Sep/16  Updated: 09/Feb/17  Resolved: 23/Sep/16

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Bug Priority: Neutral
Reporter: Hieu Nguyen Duc Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 6.5h
Original Estimate: 3d

Attachments: PNG File moveOperationError.png     PNG File pic1.png     PNG File pic2.png    
Issue Links:
Relates
relates to MGNLUI-4012 Not possible to move a property via m... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: Saigon 62
Story Points: 3

 Description   

When working on MGNLUI-4012, we noticed that Move Inside, Move After and Move Before buttons' states are not handled correctly.
We expect the button state work like the way it shows errors of move operation.
For example:
+ Move Inside button should be disabled if source node and target node are the same (pic1.png)
+ Move Before button should be disabled if target node is child node of source node (pic2.png)
...


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