FlyoutItemIsVisible property in Shell Items is always true

[gonultasmf]

Description

The following definition is made within the Shell:

<?xml version="1.0" encoding="UTF-8" ?>
<Shell
    x:Class="MauiApp4.AppShell"
    xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
    xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
    xmlns:local="clr-namespace:MauiApp4"
    Shell.FlyoutBehavior="Disabled"
    Title="MauiApp4">

    <ShellContent
        Title="Home"
        ContentTemplate="{DataTemplate local:MainPage}"
        FlyoutItemIsVisible="True"
        Route="MainPage" />

    <ShellContent
        Title="NewPage1"
        ContentTemplate="{DataTemplate local:NewPage1}"
        FlyoutItemIsVisible="False"
        Route="NewPage1" />

    <ShellContent
        Title="NewPage2"
        ContentTemplate="{DataTemplate local:NewPage2}"
        FlyoutItemIsVisible="False"
        Route="NewPage2" />

</Shell>

As you can see, only one of the ShellContent has its FlyoutItemIsVisible property set to true.

namespace MauiApp4
{
    public partial class AppShell : Shell
    {
        public AppShell()
        {
            InitializeComponent();

            var list = this.Items.Where(e => e.FlyoutItemIsVisible).ToList();
        }
    }
}

But when I debug the code; all ShellContent items have come to my list variable. When I examine it, the FlyoutItemIsVisible value of all items is True.

Steps to Reproduce

No response

Link to public reproduction project repository

No response

Version with bug

8.0.90 SR9

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

I was not able test on other platforms

Affected platform versions

No response

Did you find any workaround?

Unfortunately

Relevant log output

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• FlyoutItemIsVisible doesn't work for nested content (#23720), similarity score: 0.82
• .NET MAUI Shell - FlyoutItem - on Windows platform changing IsVisible property binding from false to true adds flyoutitem without visible title (#6925), similarity score: 0.82

Closed similar issues:

• When FlyoutItem is used instead of ShellContent, the menu item text is invisible (#14688), similarity score: 0.81
• Shell: Flyoutitems IsVisible set false - what is expected behaviour? (#7769), similarity score: 0.79
• Flyout is not refreshing when item visibility is changed (#10468), similarity score: 0.77

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[PureWeen]

I don't think this is a bug

One of the somewhat unfortunate things about Shell is that the structure in your XAML doesn't fully match the logical structure that gets created.

The Items you are filtering there are ShellItems not ShellContent

If you use Linq to SelectMany down to the ShellContent you'll notice that it is set on all of the ShellContent elements

[dotnet-policy-service]

Hi @gonultasmf. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[gonultasmf]

I understand what you mean. This is a sad thing. When I filtered as you said, I saw that it worked correctly:

namespace MauiApp4
{
    public partial class AppShell : Shell
    {
        public AppShell()
        {
            InitializeComponent();

            var visibleShellContents = this.Items
                .SelectMany(e => e.Items)
                .SelectMany(e => e.Items)
                .Where(content => content.FlyoutItemIsVisible)
                .ToList();
        }
    }
}

Thank you for your support