-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
App Shell tab icon change using Trigger cause rearrangement issue in Android , Works in IOS. #11520
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. |
Verified this issue with Visual Studio Enterprise 17.7.0 Preview 2.0. Can repro on android platform with sample cade. mauibugTabiconChange |
I am having the same issue, the menu icon jumps into existence on every page load when setting the icon using code behind, and looks janky |
Same issue here. Strange shuffling happens when changing icons from codebehind / viewModel. |
I have the same issue. It only happens on android. I hope this gets fixed |
Same Issue here |
This also occurs if you change the IsVisible property of a tab. |
Description
Changing the App Shell tab icon using style triggers causes the tab bar icon to shift and rearrange on icon change.
Works fine in IOS.
Steps to Reproduce
<ShellContent Title="Notifications" Style="{StaticResource NotificationStyle}" ContentTemplate="{DataTemplate local:NotificationsPage}" Route="NotificationsPage"/>
Link to public reproduction project repository
https://github.com/ganeshachary/mauibugTabiconChange
Version with bug
7.0 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
eg Android 23 to 33
Did you find any workaround?
Not able to find any workaround
Relevant log output
The text was updated successfully, but these errors were encountered: