-
-
Notifications
You must be signed in to change notification settings - Fork 678
NVDA causes Chrome to crash while editing a form in google forms #9364
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
Comments
randomly, NVDA can not activate focus mode when pressing enter on the listbox. In that case I get this error in the log:
|
In focus mode, Before google chrome crashes I get this errors:
|
cc: @LeonarddeR |
I can reproduce this with both Google Chrome: 72.0.3626.121 and 73.0.3683.86 Using NVDA version alpha-16976,7fc6c71f |
What about adding regression label to this? |
There are several people reporting this on Github, assigning at least P2 should be appropriate. @feerrenrut what do you think? |
Filed Chrome Issue 947898: NVDA causes Chrome to crash in IEnumVARIANT::next fetched from IAccessible::accSelection |
The issue in Chrome was resolved in version 77. It is now safe to re-enable fetching of selected items for listboxes. Original issue #9364
The issue in Chrome was resolved in version 77. It is now safe to re-enable fetching of selected items for listboxes. Original issue #9364 And original fix - For RC: #9458 - For Master: #9430 Chrome bug tracker: https://crbug.com/947898
The issue has been reported on user list in a similar way.
Steps to reproduce:
https://sites.google.com/site/secretariapiloto188cvv/diarioplantao
Actual behavior:
Google Chrome crashes
Expected behavior:
Google chrome should not crash.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2019.1 Beta 1
Windows version:
Windows 10 1809 Update
Name and version of other software in use when reproducing the issue:
Chrome 72
Other questions
Does the issue still occur after restarting your PC?
yes
Have you tried any other versions of NVDA?
Yes, the issue is not occuring in NVDA 2018.4.1.
The text was updated successfully, but these errors were encountered: