Broken #AuttoSuggestBox in a #Flyout inside of #AppBarButton on a #CommandBar

[FernandoVeras]

Describe the bug

I'm having issues when trying to use an AutoSuggestBox inside a flyout of an AppBarButton in a CommandBar. It sounds complicated, but this is the scenario in my application.

When I use the AutoSuggestBox in this way, I can only access the component via tab navigation.

The AutoSuggestBox has all the usual states, such as hover and pressed, but when you try to use the component, the UI seems to be blocked.
The component receives the click, but the cursor won't let the user write unless you go via tab navigation (check the GIF).

I can't find any solution for this problem and can't find any warning of this type of use in the Microsoft Docs, even in GPT's AI's

Why is this important?

The users can't use the component with in this specific scenario, bronking the UX flow.

Steps to reproduce the bug

• WinUI application with newest SDK

<CommandBar Content="Sample title">
    <AppBarButton Content="test">
        <AppBarButton.Flyout>
            <Flyout>
                <AutoSuggestBox x:Name="SearchExample1"
                                Width="292"
                                IsHitTestVisible="True"
                                QueryIcon="Zoom" />
            </Flyout>
        </AppBarButton.Flyout>
    </AppBarButton>
</CommandBar>

Actual behavior

In this situation, the AutoSuggestBox is not accessible by clicking on it.

Expected behavior

We can normally access the AutoSuggestBox by clicking on it.

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.8.0: 1.8.250907003

Windows version

Windows 11 (24H2): Build 26100

Additional context

No response

[Skittles2519]

You will need to update your AutoSuggestBox to include AllowFocusOnInteraction="True", or you can add it to your AppBarButton to apply to all controls inside. See related closed issue #10530

[FernandoVeras]

You will need to update your AutoSuggestBox to include AllowFocusOnInteraction="True", or you can add it to your AppBarButton to apply to all controls inside. See related closed issue #10530

Thanks! It was resolved. I've set AllowFocusOnInteraction="True" direclty on the AppBarButton