-
Notifications
You must be signed in to change notification settings - Fork 1.9k
FlexLayout.Grow="1" text cuts off instead of line break on Windows #22371
Copy link
Copy link
Open
Labels
area-layoutStackLayout, GridLayout, ContentView, AbsoluteLayout, FlexLayout, ContentPresenterStackLayout, GridLayout, ContentView, AbsoluteLayout, FlexLayout, ContentPresenterlayout-flexFlexLayout issuesFlexLayout issuesplatform/windowss/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Milestone
Metadata
Metadata
Assignees
Labels
area-layoutStackLayout, GridLayout, ContentView, AbsoluteLayout, FlexLayout, ContentPresenterStackLayout, GridLayout, ContentView, AbsoluteLayout, FlexLayout, ContentPresenterlayout-flexFlexLayout issuesFlexLayout issuesplatform/windowss/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Description
If a FlexLayout, containing multiple items with Grow set to "1" and including texts of varying lengths (such as Labels and Buttons), is added to a page, the text may get cut off when multiple items are in the same row.
On Android (normal and Samsung DeX) and iOS this bug does not occur.
If there is only one item in a Row, the text will break over multiple lines as expected:
Steps to Reproduce
Expected
The text of the Labels and Buttons breaks over multiple lines
Actual
The text of the Labels and Buttons gets cut off
Link to public reproduction project repository
No response
Version with bug
8.0.21 SR4.1
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
Windows SDK 10.22621.0
Did you find any workaround?
No response
Relevant log output
No response