Passwords spoken in WSL #11554
Milestone
Comments
|
Hi, I can’t reproduce this on the same exact configuration as you described, although I’m using NVDA alpha build to test this. Can you check if UIA is used to access consoles (NVDA menu/Preferences/Settings/Advanced)? Thanks.
|
|
Try: NVDA+n, p, s, a, tab, space, Alt+P.
That will take you to the "Speak passwords in UIA consoles (may improve
performance)" option of the Advanced settings panel.
Uncheck that (space), then press enter.
Is your problem resolved?
|
|
Yes, it works when we enable the UIA checkbox.
However, when we are into SSH session, then NVDA responds very, very
slowly. Although this is altogether a new issue.
…On 9/4/2020 10:35 AM, Joseph Lee wrote:
Hi, I can’t reproduce this on the same exact configuration as you
described, although I’m using NVDA alpha build to test this. Can you
check if UIA is used to access consoles (NVDA
menu/Preferences/Settings/Advanced)? Thanks.
From: Sascha Cowley ***@***.***>
Sent: Thursday, September 3, 2020 9:56 PM
To: nvaccess/nvda ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [nvaccess/nvda] Passwords spoken in WSL (#11554)
Steps to reproduce:
1. If not already enabled and installed, enable WSL, and install and
setup a distro (I am using Ubuntu 20.04 on WSL2, but I observed this
issue on WSL1).
2. Make sure "Speak typed characters" is enabled in NVDA.
3. Within the WSL distro, try to do something that requires a password
(EG run a command via sudo).
Actual behavior:
The password is spoken by NVDA, even though it is not displayed on screen.
Expected behavior:
The password should not be spoken, or, a masking symbol (such as "*")
should be spoken instead.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.2
Windows version:
Microsoft Windows [Version 10.0.19041.450]
Name and version of other software in use when reproducing the issue:
Windows Subsystem for Linux with Ubuntu 20.04.
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.
I believe this issue occurs in prior versions of NVDA, but am going
from memory.
If addons are disabled, is your problem still occurring?
Yes.
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes. Same result before and after.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11554> , or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4AXEG3WK36RJTRKC4HVDDSEBXMTANCNFSM4QXEMJ4A>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11554 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM5Z5HB4YRNJONKEDKLSEBYRBANCNFSM4QXEMJ4A>.
|
UIA was not being used. Enabling it fixed the issue. |
|
UIA slugs everything in many command settings, and so perhaps its a
Microsoft issue?
|
|
By default, on Windows 10 version 1607 and later, NVDA currently speaks all characters typed in consoles, whether they appear onscreen or not. Technical: I disabled typed character queuing/dispatch on Your options:
|
|
I think this issue should probably be closed (if not now, then definitely when #10964 is merged). |
seanbudd
pushed a commit
that referenced
this issue
Jun 21, 2022
…(Windows 11 Sun Valley 2) (#10964) Supersedes #9771 and #10716. Closes #1682. Closes #8653. Closes #9867. Closes #11172. Closes #11554. Summary of the issue: Microsoft has significantly improved performance and reliability of UIA console: * microsoft/terminal#4018 is an almost complete rewrite of the UIA code which makes the console's UIA implementation more closely align with the API specification. * microsoft/terminal#10886, microsoft/terminal#10925, and microsoft/terminal#11253 form a robust testing methodology for the UIA implementation, including bug fixes in response to newly added tests based on Word's UIA implementation. * microsoft/terminal#11122 removes the thousands of empty lines at the end of the console buffer, significantly improving performance and stability. Since all console text ranges are now within the text buffer's bounds, it is no longer possible for console to crash due to the manipulation by UIA clients of an out-of-bounds text range. * Countless other accessibility-related PRs too numerous to list here. We should enable UIA support on new Windows Console builds by default for performance improvement and controllable password suppression. Description of how this pull request fixes the issue: This PR: * Exposes all three options for the UIA console feature flag in the UI (replaces the UIA check box with a combo box). * Adds a runtime check to test if `apiLevel >= FORMATTED`, and use UIA in this case when the user preference is auto. This is the case on Windows 11 Sun Valley 2 (SV2) available now in beta and set for release in the second half of 2022.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
sudo).Actual behavior:
The password is spoken by NVDA, even though it is not displayed on screen.
Expected behavior:
The password should not be spoken, or, a masking symbol (such as "*") should be spoken instead.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.2
Windows version:
Microsoft Windows [Version 10.0.19041.450]
Name and version of other software in use when reproducing the issue:
Windows Subsystem for Linux with Ubuntu 20.04.
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.
I believe this issue occurs in prior versions of NVDA, but am going from memory.
If addons are disabled, is your problem still occurring?
Yes.
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes. Same result before and after.
The text was updated successfully, but these errors were encountered: