[PAGES-438] Pages editor should remember last position when switching tabs Created: 19/Oct/20  Updated: 03/Dec/21  Resolved: 19/Jul/21

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

Type: Improvement Priority: Neutral
Reporter: Jürgen Brömmer Assignee: Sang Ngo Huu
Resolution: Fixed Votes: 0
Labels: VN-Analysis, ux-improvement-selected
Remaining Estimate: Not Specified
Time Spent: 10.75d
Original Estimate: Not Specified

Issue Links:
Issue split
split from PAGES-439 Jumpy/erratic scrolling of page edito... Closed
Problem/Incident
causes PAGES-477 Added component is not focused to screen Closed
causes PAGES-506 Selected component should not be re-f... Closed
Relates
relates to PAGES-541 Magnolia pages app doesnt remember th... Closed
relates to MGNLUI-6599 Scroll to selected item does not alwa... Closed
causality
is causing PAGES-475 Handle scrolling to editing position ... Open
dependency
depends upon MGNLCE-277 Pages editor widgetset version not ma... Closed
supersession
supersedes PAGES-68 Save state and selection when moving ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Date of First Response:
Epic Link: UX improvements
Sprint: UI FW 30, UI FW 32, UI FW 33
Story Points: 8

 Description   

When editing a page in a tab in Pages, then switching tabs, and back again, the vertical position is lost, and you will need to scroll down again.

Reported by customers. Since they have quite long pages this apparently is pretty cumbersome to always scroll back to the editing position. 



 Comments   
Comment by Jürgen Brömmer [ 02/Nov/20 ]

customer feedback on this one:

"Bei der Pages App wäre meine Erwartung, dass ein Schließen eines Dialoges nicht wesentlich die Position auf der Seite ändert. Wenn ich eine neue Komponente hinzufüge, kann es entsprechend rutschen. Aber wenn ich nur etwas editiere, dann darf es nicht immer nach ganz oben springen. Die Nutzer haben schon gefragt, ob es Schmerzensgeld gibt, weil sie so viel Klicken müssen…"

 

Comment by Roman Kovařík [ 19/Jul/21 ]

Linking MGNLCE-277 as we can't release these incompatibility changes without this.

Update: all the incompatibilities removed, thus removing the dependency.

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