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
NVDA shouldn't rely on the CWD #6491
Comments
P3 because there are a limited number of situations where this would manifest. |
If an addon is doing this change directory, this is a misbehaving addon, |
It is still reproducible with the following STR:
At this point NVDA is silent additionally when restarted it is still silent, and the following is written in the log: The only way to restore NVDA to its working conditions is blinddly switch to eSpeak or OneCore, restart it, and hope for the best. |
When the trial of voices mentioned above expires it it even worse. It is no longer possible to switch to either eSpeak or OneCore so the only way to have working NVDA is to remove or reset its config. While it is definitely fault of those voices it should be improved on the NVDA side also no other screen reader suffers from this. |
NVDA shouldn't rely on the CWD of the process, because this can be changed from under us.
Some examples I've seen of this are SAPI voices from Harpo and innoetics.
Effects I've seen:
The text was updated successfully, but these errors were encountered: