Shell flyout background color does not change in .NET 7.0

[Miro382]

Description

Shell flyout background color does not change in .NET 7.0

This issue is the same as: 6552
This issue has been fixed for .NET 6.0 by PR: 6901

But this problem is still present in .NET 7.0.

Steps to Reproduce

Set in Shell FlyoutBackground.
Background of the flyout always uses the dark/light theme default.

Link to public reproduction project repository

Don't have

Version with bug

7.0 (current)

Last version that worked well

6.0.424

Affected platforms

Windows

Affected platform versions

All Windows SDK

Did you find any workaround?

No response

Relevant log output

No response

[vadimffe]

I can confirm that (Latest Visual Studio updates, NET7, NET MAUI). While setting in App.xaml:

    <Shell  FlyoutBehavior="{OnIdiom Phone=Disabled, Default=Locked}" FlyoutBackground="#555555">

While debugging background is changing, but if I stop debugging and start my app again FlyoutBackground is flushing shortly with my custom color, but then is getting a default value again which is black. I have also tried to set it in Styles.xaml, but it has no effect.

  <Style TargetType="Shell" ApplyToDerivedTypes="True">
    <Setter Property="Shell.BackgroundColor" Value="{AppThemeBinding Light={StaticResource Primary}, Dark={StaticResource Gray960}}" />
    <Setter Property="Shell.FlyoutBackground" Value="{AppThemeBinding Light={StaticResource Primary}, Dark={StaticResource Gray960}}" />
    <Setter Property="Shell.ForegroundColor" Value="{OnPlatform WinUI={StaticResource Primary}, Default={StaticResource White}}" />
    <Setter Property="Shell.TitleColor" Value="{AppThemeBinding Light={StaticResource White}, Dark={StaticResource White}}" />
    <Setter Property="Shell.DisabledColor" Value="{AppThemeBinding Light={StaticResource Gray200}, Dark={StaticResource Gray950}}" />
    <Setter Property="Shell.UnselectedColor" Value="{AppThemeBinding Light={StaticResource Gray200}, Dark={StaticResource Gray200}}" />
    <Setter Property="Shell.NavBarHasShadow" Value="False" />
    <Setter Property="Shell.TabBarBackgroundColor" Value="{AppThemeBinding Light={StaticResource White}, Dark={StaticResource Black}}" />
    <Setter Property="Shell.TabBarForegroundColor" Value="{AppThemeBinding Light={StaticResource Primary}, Dark={StaticResource White}}" />
    <Setter Property="Shell.TabBarTitleColor" Value="{AppThemeBinding Light={StaticResource Primary}, Dark={StaticResource White}}" />
    <Setter Property="Shell.TabBarUnselectedColor" Value="{AppThemeBinding Light={StaticResource Gray900}, Dark={StaticResource Gray200}}" />
  </Style>

Maybe there is something else, but searching for FlyoutBackground is not giving any other results, so I assume there are no other setting for FlyoutBackground in my test app.

Also on Windows 11 there is some strange behaviour for upper bar that gets some third colour that I have not defined anywhere:

And YES, in NET 6.0 it works and in NET 7.0 it doesn't.

Please, provide some fix.

[rneeft]

An other example: when upgrading WeatherTwentyOne example to .net 7, the menu colour is also changed to white in Windows 11.

[acrigney]

This is an issue for me, would anyone be working on this soon?

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.

[vadimffe]

Is there somebody working on this? It would be nice to get this fixed soon.

[Orgbrat]

Says above they have moved this to Backlog milestone which it should be fixed. Looks like they had it fixed in 6.0 and then broke it again in 7.0.

[acrigney]

Yes guys this is really ridiculous a small bug like this means that we can not move to .net 7. I will be making a support request for this soon it's just that when our admin changes we have to reset our support plan now I am waiting for our admins to fix it.

…

On Mon, 30 Jan 2023, 6:28 am Orgbrat, ***@***.***> wrote: Says above they have moved this to Backlog milestone which it should be fixed. Looks like they had it fixed in 6.0 and then broke it again in 7.0. — Reply to this email directly, view it on GitHub <#12325 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCSC7NOGIQNK337DFZ33R3WU3AGJANCNFSM6AAAAAATLU5OHU> . You are receiving this because you commented.Message ID: ***@***.***>

[jsuarezruiz]

Doing some test debugging the Maui Core (main branch, similar to latest 7.0 release), cannot reproduce the issue:

Could someone attach a small sample where reproduce it?