Skip to content

[Bug] The 10seconds delay is still here when openning a link with windows notifications activated on Win10  #58

@Elihpmap

Description

@Elihpmap

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)

      await notifier.NotifyAsync($"Opening {name}", $"URL: {url}");

      Process.Start(path, $"{args} \"{uri.OriginalString}\"");

to

      Process.Start(path, $"{args} \"{uri.OriginalString}\"");

      await notifier.NotifyAsync($"Opened {name}", $"URL: {url}");

(and changing the "Opening" to "Opened" to stay accurate)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions