Skip to content
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

AutoSuggestBox: input not selectable in the secondary menu of the CommandBar/Flyout #6924

Closed
2 tasks done
jp-weber opened this issue Apr 2, 2022 · 5 comments
Closed
2 tasks done
Labels
area-AutoSuggestBox area-CommandBarFlyout bug Something isn't working team-Controls Issue for the Controls team

Comments

@jp-weber
Copy link
Contributor

jp-weber commented Apr 2, 2022

Describe the bug

When an AutoSuggestBox is added to the secondary CommandBar/Flyout menu, the AutoSuggestBox input is not selectable. The AutoSuggestBox in the primary commands works as expected.

           <muxc:CommandBarFlyout 
                x:Name="CommandBarFlyout1"
                Placement="Right">
                <muxc:CommandBarFlyout.PrimaryCommands>
                    <AppBarElementContainer>
                        <AutoSuggestBox 
                        Width="200"
                        Height="40"
                        QueryIcon="Find"
                        VerticalAlignment="Center"
                        Margin="0,0,1,0" />
                    </AppBarElementContainer>
                    <AppBarButton Label="Save" Icon="Cancel" ToolTipService.ToolTip="Save"  />
                    <AppBarButton Label="Delete" Icon="Delete" ToolTipService.ToolTip="Delete"  />
                </muxc:CommandBarFlyout.PrimaryCommands>
                <muxc:CommandBarFlyout.SecondaryCommands>
                    <AppBarElementContainer>
                        <AutoSuggestBox 
                        Width="200"
                        Height="40"
                        QueryIcon="Find"
                        VerticalAlignment="Center"
                        Margin="0,0,1,0" />
                    </AppBarElementContainer>
                </muxc:CommandBarFlyout.SecondaryCommands>
            </muxc:CommandBarFlyout>

Steps to reproduce the bug

  1. Add an AutoSuggestBox with AppBarElementContainer in the secondary commands of the CommandBar/Flyout
  2. Open the CommandBar/Flyout
  3. The AutoSuggestBox input is not selectable

Expected behavior

The AutoSuggestBox should works in the same way in the secondary commands, like in the primary commands.

Screenshots

AutoSuggestBox

NuGet package version

Microsoft.UI.Xaml 2.7.1

Windows app type

  • UWP
  • Win32

Device form factor

Desktop

Windows version

Windows 10 (21H2): Build 19044

@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Apr 2, 2022
@ojhad
Copy link
Contributor

ojhad commented Apr 7, 2022

CommandBar flyout is meant for single actions in a contextual fashion. What are you trying to achieve here? Maybe a custom popup would be more appropriate?

@ojhad ojhad added needs-author-feedback Asked author to supply more information. team-Controls Issue for the Controls team area-AutoSuggestBox area-CommandBarFlyout and removed needs-triage Issue needs to be triaged by the area owners labels Apr 7, 2022
@jp-weber
Copy link
Contributor Author

jp-weber commented Apr 8, 2022

It is an example to show that the same bug exists in the CommandBar and the CommandBarFlyout. The bug should also exist in WinUI3, but I have not tested it.

This shows the error in my application by using a CommandBar in the NavigationView header for the search:
2fast_search

@ghost ghost added needs-triage Issue needs to be triaged by the area owners and removed needs-author-feedback Asked author to supply more information. labels Apr 8, 2022
@ojhad ojhad added bug Something isn't working and removed needs-triage Issue needs to be triaged by the area owners labels Apr 11, 2022
@stephtr
Copy link

stephtr commented Jan 14, 2023

Yes, it also exists in WinUI3.

CommandBar flyout is meant for single actions in a contextual fashion. What are you trying to achieve here? Maybe a custom popup would be more appropriate?

Even the TabbedCommandBar example of the Windows Community Toolkit Sample App exhibits that issue (and a use case which makes sense in my opinion). Notice that even though SelectBoxes are focusable, they can't be changed in the overflow menu:

issue.mp4

@jp-weber
Copy link
Contributor Author

Any news for the issue?

@jp-weber
Copy link
Contributor Author

#8614 (comment)

@jp-weber jp-weber closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-AutoSuggestBox area-CommandBarFlyout bug Something isn't working team-Controls Issue for the Controls team
Projects
None yet
Development

No branches or pull requests

3 participants