[PAGES-391] "move"-action of component moves the wrong component Created: 02/Oct/19  Updated: 30/Sep/21  Resolved: 30/Sep/21

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.1.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
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
Date of First Response:

 Description   

In pages app when editing a page with any component focused , moving another component by clicking the arrows button is not possible because the focused component is moved instead. Steps to reproduce (provided in SUPPORT-10433):

  1. Open a page in pages app which has more than one component.
  2. Select a component (its highlighted now)
  3. Click on the "move"-icon of another component (not highlighted)
    Result: the component where you select the move-icon is now highlighted, but the component marked before is being moved. I've observed that doing the same with edit button instead of move works fine and the last component is focused and edited as expected.

In order to avoid this awkward situation users can either select the component to move in order to highlight it before pressing move button or drag and drop the component directly (avoiding the single click in the move button).



 Comments   
Comment by Marta Kobus [ 30/Sep/21 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

 

Thank you,

The Magnolia Team

Generated at Mon Feb 12 06:18:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.