Forum Discussion
React routing on Edge
Deleted - That's an impressive list of URL Fragment related issues, but none of them are likely relevant here.
@vindiW - You can watch your network traffic to see what's going on, but the most likely explanation here is that this is related to behavior of your your authentication provider. In particular, if you have a URL fragment that goes through a set of HTTP/3xx redirects, that URL fragment is meant to be preserved, and it is, within modern browsers. However, if the server returns a HTTP/200 response (e.g. because it wants you to enter your credentials), then when it redirects back to the relying party website, that URL fragment is not automatically carried through.
If you'd like, I can take a look [personal information removed by Mod] at a NetLog for you (https://textslashplain.com/2020/01/17/capture-network-logs-from-edge-and-chrome/) to confirm.
Well, sometimes switching from one tool to another is a necessity for a company to continue to grow and offer better services to customers.