-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows ToolBarItems text size difference between page types #9279
Comments
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
In this case I'm using old fashioned navigation, not Shell. |
Just to remind. NOT a shell issue... This has to do with a ContentPage navigating to a TabbedPage using Navigation.PushAsync, stuff that works perfectly on Android and iOS (although this issue does not relate to iOS becuase the ToolBarItems are handled differently on this platform) |
Verified this issue with Visual Studio Enterprise 17.6.0 Preview 7.0. Repro on windows platform with sample project. |
This is still failing with the last updates (Visual Studio 17.8.0, .Net 8, MAUI 8.0.3) Please give some priority to this problem. |
Description
The size of the dropdown menu text displayed by a Content Page, is different to that displayed by a TabbedPage.
Here is how it displays from a ContentPage (large!!!)
Here is how it displays from a TabbedPage (much smaller, I'd say a better size)
Here is a video showing how it was tested
ToolbarTextSizeTester.mp4
Here is a link to a repro project
https://github.com/hbraasch/ToolBarTextSizeTester.git
Steps to Reproduce
Version with bug
6.0.486 (current)
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
net6.0-windows10.0.19041.0
Did you find any workaround?
No
Relevant log output
No response
The text was updated successfully, but these errors were encountered: