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 does not recognize numpad delete as the delete key #286

Closed
nvaccessAuto opened this Issue Jan 1, 2010 · 3 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Jan 1, 2010

Reported by aleksey_s on 2009-03-06 19:07

steps to reproduce

  • write a word in one of the edit fields
  • press "numpad delete" on any character you typed

    actual results

  • NVDA speaks nothing

    expected results

NVDA must announce a next character, as it does with "extended" delete key.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Jan 1, 2010

Comment 1 by mdcurran on 2009-06-24 00:21
This could be fixed by simply binding "Delete" to script_delete, ("ExtendedDelete" is already bound). However this would have to be done in many places: edit, scintilla, uia, JAB, IAccessible2... blablabla. If someone wants to do it that is fine.
However, I don't think the issue is that important as the numberpad is really used just for NVDA, in the future we may want to use the numpad delete key for something NVDA-specific.
Also moving it out of 0.6 for now.
Changes:
Milestone changed from 0.6 to None

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Jan 21, 2011

Comment 2 by mdcurran on 2011-01-21 06:04
Fixed in e7e0516.
Changes:
State: closed

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Jan 21, 2011

Comment 3 by jteh on 2011-01-21 06:44
Changes:
Milestone changed from None to 2011.1

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2011.1 milestone Nov 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment