-
Notifications
You must be signed in to change notification settings - Fork 1.9k
iOS large titles behave incorrectly #9053
Copy link
Copy link
Open
Labels
area-controls-titleviewTitleViewTitleViewplatform/ioss/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-controls-titleviewTitleViewTitleViewplatform/ioss/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
Large titles have become the standard in modern iOS, thus it should work just as it does natively to provide a smooth and familiar experience.
Two small issues exist in the Maui implementation.
The first issue
When scrolling, the large title behaves in a weird stuttering way and snaps instead of transition smoothly. This was already a bug in Xamarin.Forms, but you could correct it by using
ios:Page.UseSafeArea="False", which doesn't seem to be fixing the problem in .NET Maui.How it works in Maui:
RPReplay_Final1659031391.MP4
How should work:
RPReplay_Final1659032853.MP4
The overscroll issue
Another bug related to the large titles. When an overscroll occurs, the content moves separately from the title. This wasn't a bug in Xamarin.Forms and is new to .NET Maui
RPReplay_Final1659031410.MP4
Contributing
I haven't looked into this issue myself, but I'm planning to if I can find some spare time.
May anyone already knows what's going wrong and how to fix it.
Steps to Reproduce
Create a new .NET Maui project and follow the these steps.
Version with bug
6.0.408 (current)
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 11+
Did you find any workaround?
No response
Relevant log output
No response