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

When deleting one before the last message in the outlook express message list NVDA fails to announce new item in focus #446

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 4 comments

Comments

@nvaccessAuto
Copy link

Reported by pvagner on 2009-10-29 19:14
STR:

  1. Open your outlook express and focus the list of messages.
  2. Make sure focus is set to the item immediately before the last item in the list (the second item from the very bottom).
  3. Press the delete key.

Actual results:
NVDA stays silent and you need to use NVDA+tab or NVDA+up arrow to get the currently selected item spoken.

Expected results:
As the last message in the list gains the focus, NVDA should correctly announce to that fact.

@nvaccessAuto
Copy link
Author

Comment 1 by girish on 2013-02-15 11:22
Hi

I need more information about the version of windows and outlook express you were using.

For me it is working fine in outlook express(6) of windows xp(sp3)

@nvaccessAuto
Copy link
Author

Comment 2 by briang1 on 2013-02-16 10:12
Well, this is quite an old ticket but I do notice some sluggishness when OE is in use with lots of messages, and in other parts of OE if things take a little too long nvda is prone to just say nothing at all as if its stopped looking altogether. this will often occur, for example on a new message as the first of a new session, but cancelling and reselecting it makes it work. My guess is that the poster had quite a slow machine , probably single core like mine, and it just gave up waiting.

@LeonarddeR
Copy link
Collaborator

I'd like to suggest closing this following @jcsteh's rationale in #508

There's no point in us working on additional support for something which is now obsolete.

@jcsteh: How about adding an obsolete label for those tickets or something to identify them?

@jcsteh
Copy link
Contributor

jcsteh commented Jun 9, 2017

Agreed.

@leonardder commented on 9 Jun 2017, 04:44 GMT+10:

@jcsteh: How about adding an obsolete label for those tickets or something to identify them?

Thanks for the suggestion, but I don't think this is necessary. This is not overly common and I don't think it's something we ever need to search by, gather statistics on, etc.

Closing as won't fix.

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

3 participants