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
Links are no longer activable in E-Mails displayed using Outlook Express and other e-Mail clients #3483
Comments
Comment 1 by briang1 on 2013-08-30 11:39 Can you explain what you did, was this in a preview pane by any chance? I have never had much luck with that. I am using the main display window for emails and it just works as long as the link does not line wrap. |
Comment 2 by BachirBenanou (in reply to comment description) on 2013-08-31 12:52 Brian, this is not a question of line feeds or word wrapping. Please, note that it is something that used to work before NVDA 2013.2. Unfortunately, it no longer does. Replying to BachirBenanou:
|
Comment 3 by briang1 on 2013-08-31 13:16 I just clicked the link to this ticket from the email in the list. To reiterate, I'm using Outlook Express in windows XP with all updates up to date. |
Comment 4 by jteh on 2013-09-01 22:51 |
Comment 5 by BachirBenanou on 2013-09-05 08:27 Thanks for reading. |
Comment 6 by BachirBenanou (in reply to comment 4) on 2013-09-05 08:30 Thanks for reading.
|
Attachment NVDA-WinXpSp3.log added by BachirBenanou on 2013-11-15 09:26 |
Comment 7 by BachirBenanou on 2013-11-15 09:33 |
Comment 8 by briang1 on 2013-11-16 08:55 |
Comment 9 by briang1 on 2013-11-16 09:25 So, quite what this all proves is difficult to say, but I suppose if one always gets to links in emails with cursorrs, it could be possible, at times to not get the link to work. I've yet to get a log of this, but the normal operation log with all the arnings is pasted below. Input: kb(desktop):enter DEBUGWARNING - watchdog.watcher (08:44:46): DEBUGWARNING - scriptHandler.executeScript (08:44:46): |
Comment 10 by briang1 on 2013-11-16 09:40 |
Comment 11 by BachirBenanou (in reply to comment 10) on 2014-02-20 20:32
Hello, Sorry to insist on this matter, but it used to work and it no longer does. Other French users of Windows Live Mail are reporting the same problem of weblinks under Windows 7 not to activate as it used to with NVDA 2013.1.1. Shall we all downgrade to it? |
Comment 12 by briang1 on 2014-02-21 07:47 |
Comment 13 by msuch (in reply to comment 8) on 2014-03-11 15:26 A bit more on this problem:
|
It is very unlikely that this will ever be tracked down. Furthermore, Windows Live Mail and Outlook Express are both abandoned, closing as wontfix. |
I feel you are being draconian again.
Remember there are a lot of people still using these programs around the
world. I've not seen this issue though unless its just new today.the issues
may well be that many email software now has its own code for displaying and
handling html. this is certainly how Outlook express new developments by
third parties works. I'm using it now on windows 7 and could not do what I
do without this software as no email client offers me the same group of
features.
So just because its not being actively developed by the original people, it
does not mean its not still in use and should be supported.
Brian a great supporter of if it works then use it.
Brian
|
As several comments stated, this problem was hard to reproduce. It boiled down to an encoding issue, though the conversation comes to a halt after that observation. While not being able to activate links is serious enough, I think @LeonarddeR is saying that it will likely not be fixed for applications considered discontinued. |
Reported by BachirBenanou on 2013-08-30 11:15
Hello, Devs,
When a message is open in Outlook Express 6 for Xp, the links it may contain are no longer clickable using the space bar or the enter key.
Using insert+f7 to display the elements list does bring these up, but hitting the "Activate button" does not click the links as it as appropriate.
Other users also report this to happen using Windows Live Mail under Windows 7.
As this used to work before NVDA 2013.2, I think this tobe very important to fix. Thank you.
The text was updated successfully, but these errors were encountered: