Download Unigram from the above Store link and connect it to your account.
Create a conversation, and ensure that you have at least one reply in there:
Focus the message you want to reply to and hit Context Menu key.
Select Reply, then type your reply.
In the output list, focus your reply you just sent.
Tab once.
Actual behavior:
NVDA will speak the group info for your message, and the word "Link", but not what the link's name is.
Expected behavior:
It should speak the link's name, which is the text of the message this is a reply to. The text is a child of the link, done as a Textblock control, in accordance with this information given by Microsoft's documentation. It appears that some Edge code introduced in 2016 special cased those exact controls like links and buttons, as well as some others, to no longer retrieve the name from text if I understand the references in this code block correctly.
System configuration
NVDA installed/portable/running from source:
Installed.
NVDA version:
2019.1
Windows version:
10.0.1809 (Build 17763,379).
Name and version of other software in use when reproducing the issue:
Unigram latest version from Microsoft Store.
Other information about your system:
Not applicable.
Other questions
Does the issue still occur after restarting your PC?
Yes.
Have you tried any other versions of NVDA?
Both 2018.4 as well as latest master, both also show the issue.
Steps to reproduce:
Found while using the Unigram Telegram client, which is an UWP application.
Actual behavior:
NVDA will speak the group info for your message, and the word "Link", but not what the link's name is.
Expected behavior:
It should speak the link's name, which is the text of the message this is a reply to. The text is a child of the link, done as a Textblock control, in accordance with this information given by Microsoft's documentation. It appears that some Edge code introduced in 2016 special cased those exact controls like links and buttons, as well as some others, to no longer retrieve the name from text if I understand the references in this code block correctly.
System configuration
NVDA installed/portable/running from source:
Installed.
NVDA version:
2019.1
Windows version:
10.0.1809 (Build 17763,379).
Name and version of other software in use when reproducing the issue:
Unigram latest version from Microsoft Store.
Other information about your system:
Not applicable.
Other questions
Does the issue still occur after restarting your PC?
Yes.
Have you tried any other versions of NVDA?
Both 2018.4 as well as latest master, both also show the issue.