You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have a route path containing a unicode character, it is recommended to use encodeURI so reach router supports it correctly. This works well in all browsers but it doesn't work in MS Edge.
After some investigation, it seems that in MS Edge, the window.location.pathname is not url encoded, but other browsers encode it.
This results in not found route when a url contains a special character.
I have opened a pull request to suggest a fix, see #344
Description
When you have a route path containing a unicode character, it is recommended to use
encodeURI
so reach router supports it correctly. This works well in all browsers but it doesn't work in MS Edge.Example:
After some investigation, it seems that in MS Edge, the
window.location.pathname
is not url encoded, but other browsers encode it.This results in not found route when a url contains a special character.
I have opened a pull request to suggest a fix, see #344
Steps to reproduce
Unicode page
linkIn Chrome, you'll see the page title
Page with unicode in url works !
, but in MS Edge you don'tRelated Issues
I've discovered this bug by digging into a gatsby issue. See gatsbyjs/gatsby#17556
The text was updated successfully, but these errors were encountered: