Pressing enter on a link within an Outlook email message simply plays the NVDA error sound and does not open the default browser to the link

[nvaccessAuto]

Reported by RobertSpangler on 2015-08-01 16:28
When I open an email message, move to a link and press enter on it, NVDA plays the error sound and nothing else happens. This is in Outlook 2013. I've seen this issue in Next for a while now. Below is the error:
ERROR - scriptHandler.executeScript (12:25:58):
error executing script: <bound method MailViewerTreeInterceptor.script_activatePosition of <appModules.outlook.MailViewerTreeInterceptor object at 0x05012430>> with gesture u'enter'
Traceback (most recent call last):
File "scriptHandler.pyc", line 186, in executeScript
File "browseMode.pyc", line 289, in script_activatePosition
File "browseMode.pyc", line 979, in activatePosition
File "browseMode.pyc", line 948, in activateNVDAObject
File "NVDAObjects\IAccessible__init.pyc", line 746, in doAction
NotImplementedError

Please let me know if anything else is needed.

[nvaccessAuto]

Comment 1 by briang1 on 2015-08-01 16:41
Hmm, it says not implimented, so one assumes that is why its not working. Did it used to work previously? For what its worth, Old Outlook Express and Live mail links work as long as the do not bridge lines.

[nvaccessAuto]

Comment 2 by RobertSpangler (in reply to comment 1) on 2015-08-01 17:04
Replying to briang1:

Hmm, it says not implimented, so one assumes that is why its not working. Did it used to work previously? For what its worth, Old Outlook Express and Live mail links work as long as the do not bridge lines.

It is not an issue in the stable branch.

[nvaccessAuto]

Comment 3 by jteh on 2015-08-12 04:33
Probably a regression introduced by #5212.
Changes:
Milestone changed from None to 2015.3

[nvaccessAuto]

Comment 4 by Michael Curran <mick@... on 2015-08-12 09:18
In [02b8eee]:

Winword treeInterceptor's _activatePosition method:  call activate  on the TextInfo as that is where Winword's activation implementation is. Perhaps in future we may want to relook at how this is abstracted, but this directly fixes #5258

Changes:
State: closed