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

WinUI: Mouse tracking fails in applications using Windows App SDK 1.6. #17407

Open
hwf1324 opened this issue Nov 16, 2024 · 4 comments
Open

WinUI: Mouse tracking fails in applications using Windows App SDK 1.6. #17407

hwf1324 opened this issue Nov 16, 2024 · 4 comments
Labels
blocked/needs-external-fix blocked/needs-info The issue can not be progressed until more information is provided. needs-triage

Comments

@hwf1324
Copy link
Contributor

hwf1324 commented Nov 16, 2024

Steps to reproduce:

In a WinUI application using the Windows App SDK 1.6.
Perform mouse tracking.

Actual behavior:

Does not report what is under the mouse.

Expected behavior:

Report what's under the mouse

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

install

NVDA version:

alpha-34581,32245d46 x86

Windows version:

Windows 11 22H2 (10.0.22621) workstation AMD64

Name and version of other software in use when reproducing the issue:

WinUI application using Windows App SDK 1.6.
For example, PowerToys v0.86.0
Or create a blank WinUI app in VS 2022

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes

@hwf1324
Copy link
Contributor Author

hwf1324 commented Nov 16, 2024

Hi, CC: @josephsl , @michaelDCurran , Maybe you guys will have some thoughts on this issue.

It's strange that NVDA considers the external window and pane objects of these apps to be IAccessible, while internally they are normal UIA objects, perhaps this is the cause of the problem?

But I don't know what it's because of, and both the narrator and Accessibility Insights For Windows are able to get the internal controls with the mouse.

@seanbudd
Copy link
Member

Has this been reported to microsoft? Have you tested this with the latest release 1.6.3?

It seems like this SDK is new and under active development. Bugs should be reported to the authors primarily.

@seanbudd seanbudd added blocked/needs-external-fix blocked/needs-info The issue can not be progressed until more information is provided. needs-triage labels Nov 19, 2024
@hwf1324
Copy link
Contributor Author

hwf1324 commented Nov 19, 2024

The issue has been reported to the Windows App SDK team, but there has been no response yet.

There are already official versions of some apps that have encountered this problem, such as PowerToys v0.86.0, UniGetUI, and others.

@josephsl
Copy link
Collaborator

josephsl commented Nov 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/needs-external-fix blocked/needs-info The issue can not be progressed until more information is provided. needs-triage
Projects
None yet
Development

No branches or pull requests

3 participants