Ticket #200 (closed defect: fixed)

Opened 3 years ago

Last modified 21 months ago

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

Reported by: mike.reiser Owned by:
Priority: minor Milestone: 2010.2
Component: Core Version: 2010.1beta1
Keywords: Cc:
Operating system: Blocked by: #40, #643
Blocking:

Description (last modified by m11chen) (diff)

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.

Change History

comment:1 Changed 3 years ago by jteh

  • Priority changed from major to minor
  • Milestone 0.6 deleted

comment:2 Changed 23 months ago by m11chen

  • Status changed from new to assigned
  • Description modified (diff)
  • Component changed from Core to Virtual buffers
  • Owner set to m11chen
  • Version changed from development to 2010.1beta1
  • Milestone set to 2010.2
  • Keywords Windows live messenger input message added
  • Operating system set to Windows 7

comment:3 Changed 23 months ago by jteh

  • Keywords Windows live messenger input message removed
  • Operating system Windows 7 deleted
  • Component changed from Virtual buffers to Core
  • Blocked by 40 added
  • Milestone changed from 2010.2 to 2010.3

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.

comment:4 Changed 23 months ago by jteh

  • Owner m11chen deleted

comment:5 Changed 21 months ago by mdcurran

  • Blocked by 643 added; 40 removed

Implemented in changeset:displayModel,3464.1.10
Once displayModel branch is merged this can be closed.

comment:6 Changed 21 months ago by jteh

  • Status changed from assigned to closed
  • Resolution set to fixed

Implemented via display hooking merged in changeset:main,3508.

comment:7 Changed 21 months ago by jteh

  • Milestone changed from 2010.3 to 2010.2
Note: See TracTickets for help on using tickets.