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

Focus does not move into the frame after navigating to one from a navigation view. #9631

Closed
dhoehna opened this issue May 13, 2024 · 2 comments
Labels
area-NavigationView NavView control bug Something isn't working team-Controls Issue for the Controls team

Comments

@dhoehna
Copy link

dhoehna commented May 13, 2024

Describe the bug

After selecting an item in a navigation view, focus should move to the first focusable element inside the frame. Instead focus stays in the navigation view.

Steps to reproduce the bug

  1. Make a simple app with a navigation view and a frame.
  2. Add a new page with a button.
  3. Make a SelectionChanged event.
  4. In the event, navigate to the page made earlier.

Expected behavior

Focus moves to the button inside the frame.

Screenshots

NavigationViewTabOrder.mp4

NuGet package version

WinUI 3 - Windows App SDK 1.5.3: 1.5.240428000

Windows version

Windows Insider Build (xxxxx)

Additional context

No response

@dhoehna dhoehna added the bug Something isn't working label May 13, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label May 13, 2024
Copy link

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. Thank you!

Open similar issues:

Closed similar issues:

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

@kmgallahan
Copy link
Contributor

NavigationView has no knowledge of the Frame you are using, or if it is being used with a Frame at all. It merely reports user interactions and you are responsible for determining what to do with them.

If that means you call a method on Frame to display some content, then you need to decide what to do after that content loads. That might mean focusing on something in the Frame, but that is up to the developer and is not something NavigationView should try to figure out by making assumptions.

@codendone codendone added area-NavigationView NavView control team-Controls Issue for the Controls team and removed needs-triage Issue needs to be triaged by the area owners labels May 23, 2024
@ranjeshj ranjeshj closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-NavigationView NavView control bug Something isn't working team-Controls Issue for the Controls team
Projects
None yet
Development

No branches or pull requests

4 participants