-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Bug] The 10seconds delay is still here when openning a link with windows notifications activated on Win10 #58
Comments
That's the right fix. I had meant to include a change like that in the referenced commit, but I overlooked it. I will gladly merge in a PR with this proposed change. |
I closed the PR because this fix brings back the tray icon not dissapearing issue... |
I will investigate this in the next day or two. Thanks for your trouble. |
Version 0.12.6 is working as expected on Win10 and Win11. |
Not with notifications enabled though... at least not on my PC?
Thanks for your help too! |
You're right, I must have a made a mistake. I tried it again on 0.12.6 and got the 10s delay. Let me see what I can do... |
I have a fix, could you try it in the linked PR? Your previous PR was good, but additionally, we now have to catch any exception from |
Thank you ! |
I'll look into the 10s delay on the nonfirst URL |
As we discuted previously there was an issue on Windows 10 where the notification service was delaying the opening of the link to after the notification disappeared (10 second delay)
A fix was proposed in commit 2b10586caa1e4f90d0949fa845a4364e947e2005 but since the new task is still awaited, the focus still doesn't come back to the BrowserService.LaunchAsync() to launch the URL until it is finished (= until the notification has finished being displayed).
The easiest solution to me (without impacting the await uses since that wasn't a good idea last time ) would be to exchange these two lines in BrowserService.cs (lines 41 and 43)
to
(and changing the "Opening" to "Opened" to stay accurate)
The text was updated successfully, but these errors were encountered: