nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.11k stars 637 forks source link

Deleting text in browse mode for Word should be blocked #5437

Open nvaccessAuto opened 9 years ago

nvaccessAuto commented 9 years ago

Reported by leonarddr on 2015-10-23 10:51 As reported in #2975 comment83, it is possible to delete text with backspace and delete in MS Word. Since browse mode for Word is there for quite some time, I thought it would be best to open a new ticket for this, as this issue has not been picked up yet.

LeonarddeR commented 7 years ago

Honestly, I still belief that "Trap all non-command gestures from reaching the document" should block both delete and backspace.

derekriemer commented 7 years ago

but that would block going back.

derekriemer commented 7 years ago

retract that, this is specifically for word.

LeonarddeR commented 7 years ago

Yes, but that means we should block certain keys to for specific apps.

jcsteh commented 7 years ago

@leonardder commented on 9 Jul 2017, 03:30 GMT+10:

Yes, but that means we should block certain keys to for specific apps.

That would be tricky. The definition of what is considered a command key (and thus what is considered a non-command key) is global to NVDA, not app specific. Also, if you're focused in an editable text field on the web, backspace should arguably be blocked in that case. Finally, backspace should probably still be spoken as a command key, not a typed character, so we'd need to come up with some other concept for these keys that should be blocked when in browse mode.

I'll give this a p3 because users see backspace and delete the same as they see typed characters in this case and this inconsistency could result in text being accidentally removed. On the flip side, we don't have any solid ideas on how to implement this, so fixing this isn't trivial.

Adriani90 commented 5 years ago

@mltony I don't know if you want to focus only on browsers, but maybe this is also a bug which can be fixed with your browse mode method.