-
Notifications
You must be signed in to change notification settings - Fork 677
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
NavView: Navigation does not work when using Narrator in Scan Mode #7274
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Looks like NavViewItem AP not supporting Invoke pattern was an intentional change: |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Since we don't want to add Invoke back to NavViewItem AP (because of #2702), we instead double up UIA SelectionItem.Select() to also do an invoke. This makes SelectionItem.Select() equivalent to clicking on the item which is what desired in most cases. |
@ojhad can you take a look at the latest iteration? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
NavViewItem AutomationPeer was intended to support Invoke Pattern, but didn't return correctly for GetPatternCore.
Not supporting Invoke causes problems when interacting with NavView via UIA, particularly when using Scan Mode in Narrator.
Closes #5998