Blind and Visually Impaired Community
↑
5
↓
Critical bug with vscode and nvda, does any one know how to fix? (self.Blind)
submitted by vzjiofdanefnlk
const sayHi = () => {
console.log("hi");
};
When I navigate words by pressing ctrl + arrow on this code, it reads "sayHi equals" at the function name, and also at the equal sign, it reads "sayHi equals" again.
So, it reads "sayHi equals" twices. This is super confusing, does anyone know how to fix this?
console.log("hi");
};
When I navigate words by pressing ctrl + arrow on this code, it reads "sayHi equals" at the function name, and also at the equal sign, it reads "sayHi equals" again.
So, it reads "sayHi equals" twices. This is super confusing, does anyone know how to fix this?
nadmaximus 3 points 1y ago
I wonder if it's seeing the second equals (in the =>) as another equal sign and the parens are empty so it just backs up to repeat sayHi.
If you remove the =>, does it still repeat? (obviously you need the =>, but you could also phrase it as a function() instead. Which would be annoying.
There is an addon called $1 which claims to improve intellisense and such. I have not used it.
I am sighted but I often have nvda active while testing my projects, and it just babbles away while I code. So I have some sense of how it works with vscode, but I never actually *use* it.
Good Luck.
If you remove the =>, does it still repeat? (obviously you need the =>, but you could also phrase it as a function() instead. Which would be annoying.
There is an addon called $1 which claims to improve intellisense and such. I have not used it.
I am sighted but I often have nvda active while testing my projects, and it just babbles away while I code. So I have some sense of how it works with vscode, but I never actually *use* it.
Good Luck.
vzjiofdanefnlk [OP] 2 points 1y ago
It still repeats, if I remove the =>.
It happened, even when the text was just "sayHi =".
It seems like sayHi and = are considered as one word in a way, so nvda read it together while word navigating.
But somehow the caret can go to the next to equals too and both sayHi and = are pronounced "sayHi equals"
Oh wait, it's happening right now too, it's not vscode thing then
It happened, even when the text was just "sayHi =".
It seems like sayHi and = are considered as one word in a way, so nvda read it together while word navigating.
But somehow the caret can go to the next to equals too and both sayHi and = are pronounced "sayHi equals"
Oh wait, it's happening right now too, it's not vscode thing then
nadmaximus 2 points 1y ago
Weird! Looks like from bug reports NVDA may have a general problem with repeating things. I don't see anything specific to vscode or equals.
It's got to be annoying to find a tool that almost works but has some bug that makes it frustrating to depend on. The bug reports go back to 2020 at least and apparently still going on.
I bet you're not going to find a fix until NVDA fixes it.
It's got to be annoying to find a tool that almost works but has some bug that makes it frustrating to depend on. The bug reports go back to 2020 at least and apparently still going on.
I bet you're not going to find a fix until NVDA fixes it.
vzjiofdanefnlk [OP] 2 points 1y ago
Sorry it wasn't happening here
It happens on vscode with =, +, >
Yeah, I wonder if other people are coding with this bug alive
thank for the help tho
It happens on vscode with =, +, >
Yeah, I wonder if other people are coding with this bug alive
thank for the help tho
mehgcap 1 points 1y ago
This is a known problem. As I recall, it's something in the Chrome rendering engine and how that exposes text to screen readers, then how NVDA interacts with the text. There's a setting to control what VSCode considers word boundaries, which should come up if you search for it online. I can try to find it and post something here later if you can't find anything.
vzjiofdanefnlk [OP] 1 points 1y ago
https://github.com/nvaccess/nvda/issues/10105
I found this, but I couldn't see any workaround to fix this.
Is there a setting to fix?
I found this, but I couldn't see any workaround to fix this.
Is there a setting to fix?
mehgcap 1 points 1y ago
The problem is Chromium, according to some VSCode developers. Here's the issue from last year that tracked all the word navigation issues:
https://github.com/microsoft/vscode/issues/90578
https://github.com/microsoft/vscode/issues/90578
This nonprofit website is run by volunteers.
Please contribute if you can. Thank you!
Our mission is to provide everyone with access to large-
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
©2023 HumbleCat Inc • HumbleCat is a 501(c)3 nonprofit based in Michigan, USA.