In windows live messenger, nvda does not allow reviewing of entered text #200

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

1 participant

@nvaccessAuto

Reported by mike.reiser on 2008-10-17 03:27
This has been posted a while ago, and the problem still persists in the current version Windows Live Messenger bild 14.0.8089.726 with NVDA 2010.1 Beta. I'm not sure if someone is working on anything related that might help solve the issue. However, after searching the tickets and users communities, I couldn't find any recent updates directly related to the problem described. I thought I might try updating this ticket before posting a new one.

Just was testing NVDA r2432 with the current version of windows live messenger. While it reads outgoing and incomeing messages, it does not allow one to review what they've entered into the input field IE for backspacing of characters and reading by character/line etc. Instead when backspace or any arrow key is pressed, silence happens.

Blocked by #643

@nvaccessAuto

Comment 1 by jteh on 2008-12-05 03:00
Changes:
Milestone changed from 0.6 to None

@nvaccessAuto

Comment 2 by m11chen on 2010-03-23 09:15
Changes:
Milestone changed from None to 2010.2

@nvaccessAuto

Comment 3 by jteh on 2010-03-23 10:53
Please don't change these fields unless you're certain about the change. For example, this is definitely not a virtual buffer related issue.

This issue requires display hooks to fix.
Changes:
Milestone changed from 2010.2 to 2010.3

@nvaccessAuto

Comment 5 by mdcurran on 2010-05-10 07:35
Implemented in displayModel,3464.1.10
Once displayModel branch is merged this can be closed.

@nvaccessAuto

Comment 6 by jteh on 2010-05-13 04:06
Implemented via display hooking merged in c90061b.
Changes:
State: closed

@nvaccessAuto

Comment 7 by jteh on 2010-05-13 04:06
Changes:
Milestone changed from 2010.3 to 2010.2

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2010.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment