Forum Discussion
Solved
Edge 128.0.2739.42 crashes when user clicks on custom URI
We have a small custom app to allow us to open file links from our intranet site. We created a custom uri handler and it has been working up until Edge Version 128.0.2739.42 . With version 128 clic...
- I've just fixed (cludged!) our issues by changing all hyperlinks and window.open statements which call our custom protocol so that they use a target of '_self' . Some used '_blank', others didn't specify anything.
Everything's now working.
However - for Microsoft / Google if you're reading - this is a workaround and the underlying problem needs to be fixed.
THaack
We have the same problem in our company.
The two common conditions of the PCs that are having the problem are.
- They are logged into Windows with a M365 account.
- They are using the version 128 of Edge.
The version 127 of Edge did not cause the problem in the environment where a user logs in with his M365 account. After updating to 128, he gets the same problem.
The same problem occurs with latest Google Chrome (ver.128) in our environments where the problem of Edge occurs, but not with FireFox.
Updated:
Our protocol handler is listed in a "URL Allow list" which is distributed as a InTune policy. The problem can be avoided by changing the protocol name in the list.
https://support.google.com/chrome/a/thread/292536913?hl=en&msgid=293182926
I've just fixed (cludged!) our issues by changing all hyperlinks and window.open statements which call our custom protocol so that they use a target of '_self' . Some used '_blank', others didn't specify anything.
Everything's now working.
However - for Microsoft / Google if you're reading - this is a workaround and the underlying problem needs to be fixed.
Everything's now working.
However - for Microsoft / Google if you're reading - this is a workaround and the underlying problem needs to be fixed.