[MGNLUI-5330] Default editor layout renders complex field regardless the property ordering Created: 19/Aug/19  Updated: 16/Jan/20  Resolved: 16/Jan/20

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

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1h
Time Spent: 0.5h
Original Estimate: Not Specified

Attachments: PNG File image-2019-08-19-13-31-24-025.png    
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:
Epic Link: UI framework: forms, dialogs, content editing
Sprint: UI Framework 5, UI Framework 6, UI Framework 14
Story Points: 1

 Description   

When layout isn't specified form engine should fall back to a single-tab layout that renders the components as they show up in the property list.

However, the complex fields seem to appear at random positions (see attached screenshot, the upload field composition should've been in the first position).



 Comments   
Comment by Roman Kovařík [ 07/Jan/20 ]

Reopened: Regression, fix and add a test.

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