Replies: 2 comments
-
cc a relevant discussion from discord - https://discord.com/channels/770287896669978684/770287896669978687/1009126322162901103 |
Beta Was this translation helpful? Give feedback.
-
BFCache is quite controversial. Some people really want it to work in their application, while others find it disruptive. Currently, the topic of BFCache is heavily discussed in the context of RouteCache in NextJS. Next has added a cache for back/forward navigation in the new AppRouter, which causes major problems for applications whose state is controlled by the backend (Deep Dive: Caching and Revalidating · vercel/next.js · Discussion #54075 (github.com)). Personally, I believe that such behavior can be added, but it should be 100% possible to "opt-in" or "opt-out". For me, for example, the new behavior is a total blocker in the context of migrating from Page Router to App Router. |
Beta Was this translation helpful? Give feedback.
-
When navigating back and forward, the browser will cache the history stack - https://web.dev/bfcache/
This makes a huge difference in performance -
Screen.Recording.2023-06-19.at.1.34.59.AM.mov
On iOS safari, gesture navigation results in terrible UX -
RPReplay_Final1687119020.MP4
Is there any way remix can emulate this behaviour when using client-side navigation via
<Link>
s?Beta Was this translation helpful? Give feedback.
All reactions