[MAGNOLIA-4822] Display all edit bars along the active path to give more context in edit mode Created: 07/Feb/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: admininterface, page editor
Affects Version/s: 4.5.6
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Mike Wilson Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File magnolia45improvedEditBars.js    
Issue Links:
relation
is related to MAGNOLIA-4821 Clicking component bar doesn't open c... 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:

 Description   

When editing components on a page with several levels of areas and components in Magnolia, the experience is a bit flickery as edit bars that were previously displayed are getting hidden when moving further down the hierarchy.

An example of this is shown in this video:
http://www.screenr.com/7n47
(fullscreen recommended)

I suggest that all edit bars on the active path (between root and the active position) stays displayed, to avoid flickering and to provide a better context of where the active component is located.
To further improve the experience I also suggest that:

  • clicking an edit bar will always open the contained level of edit bars
  • also display edit bars of siblings to the areas and components of the active path

Here is a video showing the same page with this improved behaviour:
http://www.screenr.com/Cn47
(fullscreen recommended)

To try out the improved behaviour, include the attached JavaScript file in edit mode.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

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 03:59:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.