Skip to content
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

Problem when deleting a selection in Microsoft Word, NVDA does not announce "Selected deleted" and NVDA does not announce the text that has followed the previously selected the word "Unchecked", when you move the focus #779

Closed
nvaccessAuto opened this issue Jul 23, 2010 · 7 comments

Comments

@nvaccessAuto
Copy link

Reported by jeronimo on 2010-07-23 11:41
In Microsoft Word, when you want to delete a selection, NVDA does not announce "Selected deleted" as he does in WordPad or Notepad in Windows and NVDA does not announce the text that has followed the previously selected the word "Unchecked", when you move the focus.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-07-23 12:12
Changes:
Milestone changed from 2010.2 to 2010.3

@nvaccessAuto
Copy link
Author

Comment 2 by mdcurran on 2010-12-01 07:04
Considering Changing script_delete and backspace to be more smart as they are aware they are deleting if the selection changes in anyway.

@nvaccessAuto
Copy link
Author

Comment 3 by mdcurran on 2010-12-13 23:56
Some technical info:

  1. winword NVDAObject is an EditableTextWithoutAutoSelectDetection, and it can not use auto select detection as caret events are a little bit flaky... we sometimes get them, we sometimes don't.
  2. script_caret_delete in this case would need to manually call speakSelectionChange passing it TextInfos from the caret before and after sending the key press.
  3. It has been found that Microsoft Word range objects mutate when text is inserted/deleted in a document (e.g. a document with the text "Hello world" and you have a range containing the "wo" in world and you then go and delete the "wo" the range will now be collapsed at the r of world, rather than expanded to "rl").

Because of all this, it would be rather hard to support this feature without rewriting the MS Word TextInfo to only use offsets and keep moving a temporary range object each time it needed to find something out.
Probably not something we should do for this release.
Changes:
Milestone changed from 2011.1 to near-term

@nvaccessAuto nvaccessAuto added this to the near-term milestone Nov 10, 2015
@jcsteh jcsteh removed this from the near-term milestone Jun 24, 2016
@LeonarddeR
Copy link
Collaborator

It is not clear to me how to reproduce this particular issue, but I recall reading about it in another ticket.

@ruifontes
Copy link
Contributor

ruifontes commented Jul 4, 2017 via email

@ruifontes
Copy link
Contributor

ruifontes commented Jul 4, 2017 via email

@ehollig
Copy link
Collaborator

ehollig commented Sep 16, 2017

Thank you @ruifontes for the steps to reproduce. Closing as I believe this to be an duplicate of #510.
Duplicate of #510

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

No branches or pull requests

6 participants