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
I am unable to get <Link>s to work when using createBrowserRouter in devices which use a very old browser. Updating the browser is not an option.. The userAgent is Mozilla/5.0 (Linux; x86_64 GNU/Linux) AppleWebKit/601.1 (KHTML, like Gecko) Version/8.0 Safari/601.1 WPE, so I believe that is similar to Safari 8 from 2014. I have been able to use <BrowserRouter>, <Routes>, and <Route>. When using createBrowserRouter, the <Link>s do not seem to do anything.
The device with the old browser has no access to dev tools or the console. By surfacing some info in the UI, I determined the const location = useLocation() does not update the key property in the old browser, but does in the working modern browsers. Any ideas why this is? Could it be a bug? I would be happy to make an example, but do not know of anywhere I can publicly run such an old browser to share my woes. This is all happening on a proprietary browser embedded in hardware I have on my desk :-(
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am unable to get
<Link>
s to work when using createBrowserRouter in devices which use a very old browser. Updating the browser is not an option.. The userAgent is Mozilla/5.0 (Linux; x86_64 GNU/Linux) AppleWebKit/601.1 (KHTML, like Gecko) Version/8.0 Safari/601.1 WPE, so I believe that is similar to Safari 8 from 2014. I have been able to use<BrowserRouter>
,<Routes>
, and<Route>
. When using createBrowserRouter, the<Link>
s do not seem to do anything.The device with the old browser has no access to dev tools or the console. By surfacing some info in the UI, I determined the const location = useLocation() does not update the key property in the old browser, but does in the working modern browsers. Any ideas why this is? Could it be a bug? I would be happy to make an example, but do not know of anywhere I can publicly run such an old browser to share my woes. This is all happening on a proprietary browser embedded in hardware I have on my desk :-(
Beta Was this translation helpful? Give feedback.
All reactions