-
-
Notifications
You must be signed in to change notification settings - Fork 475
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
Link opening is totally broken with touch/pen #2545
Comments
Report to Microsoft |
Well, if the issue is "Microsoft" please provide some helpful context and specify it's something related to the os/winui/uwp/whatever I cannot reach out to Microsoft and tell and say "Fela said it's your fault" |
I have no clue and I don't care, I just know that's not Unigram fault and I'm not going to investigate into this. |
I am a simple user who spent 5 minutes investigating this problem and opening this issue, also after other people complained about it. This affects in a crucial way touch users, since they cannot open a simple link and I don't understand why you are behaving in a so mad way for a simple report. |
I'm not behaving in a mad way, I'm just saying that's definitely not Unigram problem and some other users have confirmed that the problem appeared after a specific Windows 11 update. |
This should've been the reply since the beginning. I'm in the beta channel and considering the short amount of Unigram updates, it makes more sense to think about Windows 11 rather than Unigram or WinUI, since I would've most likely reported the issue after the Unigram update. |
Then we need to vote for my report https://aka.ms/AAf9ns8 |
This is a proper report instead microsoft/microsoft-ui-xaml#6513 |
You can fix this bug by adding |
The other way to fix this is to set, when you create the |
Describe the bug
Link opening is totally broken with touch/pen since some updates. I can reproduce it from chat messages and group/chat description
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Open the link
Version Info
The text was updated successfully, but these errors were encountered: