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
In Excel, NVDA often decides that you haven't moved, even when you have #3558
Comments
Comment 1 by mdcurran on 2013-10-03 03:23 |
Comment 2 by camlorn on 2013-10-03 04:00 |
Comment 3 by tspivey on 2013-10-13 09:26
|
Comment 4 by mdcurran on 2013-10-18 06:01 |
Comment 5 by camlorn on 2013-10-18 15:30 |
Comment 6 by mdcurran (in reply to comment 5) on 2013-11-11 04:17 |
Comment 7 by camlorn on 2013-11-12 02:51 |
Comment 9 by Michael Curran <mick@... on 2013-11-12 04:34
Changes:
|
Comment 10 by Michael Curran <mick@... on 2013-11-26 05:57
Changes:
|
Comment 11 by mdcurran on 2013-11-26 05:58 |
Reported by camlorn on 2013-10-03 01:27
Sorry for the poor summary. I couldn't think of a good one that conveyed this concisely.
In Excel 2010, when moving across an Excel spreadsheet, NVDA is periodically deciding that you haven't actually moved. It will read the cell you just left instead of the cell you arrived at and will continue to insist that you are on the cell you just left in every way. It seems to detect that you tried to move, as it does reread the cell. I haven't been able to narrow this down to a specific procedure. Sometimes, it doesn't happen. Sometimes, it's so bad that you can only effectively read every other cell. It isn't a specific spreadsheet, and it happens on both my computers. For me, this happens with 2013.2 as well as the next branch. I'm using Excel a lot for college, and this periodically renders it unusable. Restarting NVDA sometimes helps, but sometimes does nothing.
Blocking #2920, #3586
The text was updated successfully, but these errors were encountered: