Forum Discussion
Edge 128.0.2739.42 crashes when user clicks on custom URI
- Aug 29, 2024I'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 exactly this same behaviour, started yesterday after the upgrade to 128.0.2739.42.
We have a custom protocol to enable us to open a client side app from the browser, and it's been working perfectly until yesterday. Now when someone clicks a link which uses that protocol Edge closes automatically, and upon restarting offers us the chance to restore.
I haven't yet tested the right-click to see if that works but a temporary workaround for now has been to use IEMode for a particular URL path but we need a fix for the actual problem. Interesting Chrome - which also updated yesterday - works perfectly, as does Firefox.
You can use GP to rollback to edge 127 as well. That's what we've done.
https://learn.microsoft.com/en-us/deployedge/edge-learnmore-rollback