[MGNLUI-858] The page edit bar should always remain sticky at the top of the page Created: 07/Mar/13  Updated: 24/May/13  Resolved: 24/May/13

Status: Closed
Project: Magnolia UI
Component/s: page editor
Affects Version/s: None
Fix Version/s: 5.0

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: review-ux-201303, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Device: Safari 6.0.2, Mac OS X 10.8.2
Build: magnolia_bundle-stable #19


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

 Description   

As was the case in 4.5, the page edit bar should be sticky and always remain at the top of a page being edited in the page editor. If you click on the bar, the page should jump or quickly scroll to the top.

The advantages of having a sticky page bar are:

  • there's a clear, easy and quick way to select a page (clicking on the background might not be obvious or even possible).
  • we can permanently show certain key information about a page: its URI, window title and the publication status.
  • an always visible page bar acts as an immediately recognizable visual landmark of the editing view of a page.
  • click or tap on the page edit bar allows you to quickly jump to the top of the page being edited.

If you switch to a tab where a page is being edited, the green bar at the top helps you to recognize what you're looking at. In 5.0, where there's additional chrome available around the actually edited page, this may even be more the case, but can actually also be used to a greater effect than 4.5.



 Comments   
Comment by Andreas Weder [ 24/May/13 ]

This has been fixed in beta 2.

Generated at Mon Feb 12 08:41:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.