[MGNLUI-3948] Post-transition dialog has a broken layout Created: 13/Jul/16  Updated: 25/Oct/18  Resolved: 25/Oct/18

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

Type: Bug Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File change.png     PNG File move.png    
Issue Links:
Relates
relates to MGNLUI-3895 Small layouting problem in the "move"... Closed
relates to MGNLUI-3905 German language is causing design irr... Closed
relation
is related to MGNLUI-3895 Small layouting problem in the "move"... 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

 Description   

The following procedure shows the problem:

1. Open the Pages app
2. Click on one
3. Click on Move page
4. Notice the layout
5. Click on a page
6. The correct layout is shown

However, a slight layout alteration in MGNLUI-3905 (in progress) reveals that the problem is general and not limited to the Move dialog, cf. the attached screenshots. On the current demo, the problem is limited to the gray, half-visible area of the Move dialog. Only with the refactoring of the buttons do we also see the buttons popping from the window just after the transition, going back to their correct place when some action refreshes the view.

Update with MGNLUI-3905 merged: the status there is that the CSS zooming breaks the layout. apchelintcev looked at it and suggested a proper loading mechanism should be implemented sometime in the future. See MGNLUI-3905's diff to overlay-admincentral.scss for more details. For the time being, though, everything seems to work just fine as is.


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