Open Qchristensen opened 2 weeks ago
I can also confirm the same thing is happening on Edge.
System configuration NVDA installed/portable/running from source: NVDA version: NVDA 2024.4 installed Windows version: Edition Windows 11 Home Version 24H2 Installed on 10/11/2024 OS build 26120.2200 Experience Windows Feature Experience Pack 1000.26100.33.0 Name and version of other software in use when reproducing the issue: Microsoft Edge Version 131.0.2903.14 (Official build) stable app, beta channel (64-bit) Chrome Version 130.0.6723.92 (Official Build) (64-bit) 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
Very odd. using GitHub's sign in page, Microsoft Edge seems to read the Autofill dialog without issue. However with Google Chrome, the choice autopopulates, but if you clear Chrome's fill, I can confirm NVDA also says "blank". Narrator does read Chrome's autofill implementation though with some success.
Steps to reproduce:
Actual behavior:
At Step 3 NVDA either reads "blank" or whatever text was typed into the edit field already.
Expected behavior:
It should report the suggestion which currently has focus.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA version:
NVDA 2024.4 installed
Windows version:
Windows 11 (64-bit) Version: 23H2, Build: 22631.4391
Name and version of other software in use when reproducing the issue:
Chrome Version: 130.0.6723.92
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.
Tried back to NVDA 2021.3.5. Also tried 2024.4 with UIA in Chromium set to various values without any difference.
If NVDA add-ons are disabled, is your problem still occurring?
No add-ons.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?