[iOS] Page swipe issues when beforeLoad runs an async fetch
On swipe back on iOS (safari), it would briefly flash the previous screen and then load the correct screen. This issue also exists on TS Start.
Has anyone figured out a way to make this be less noticeable?
I've looked across the internet and it seems to be a prevalent issue in client-side routing and iOS's "page preview" thing.
It looks like I uploaded a screenshot and not the video, give me a second haha
7 Replies
unwilling-turquoise•8mo ago
can you provide some more resources about the iOS thing here?
are there any known fixes?
exotic-emeraldOP•8mo ago
@Manuel Schiller
One of the bigger issues i've found on this is https://github.com/remix-run/remix/issues/7936. This issue has links to similar issues in other frameworks:
https://github.com/sveltejs/kit/issues/10700
https://github.com/vercel/next.js/issues/57243 (NextJS 13)
https://github.com/nuxt/nuxt/issues/6101
It was also brought up in a Remix Discord thread back in 2020 and Ryan responded (see screenshot, responding to a video similar to the one I've posted)
Potential fixes outlined in one of the issues is overriding the swipe gesture on iOS devices, or disabling swipe overall which feels icky to me.
GitHub
Issues · remix-run/remix
Build Better Websites. Create modern, resilient user experiences with web fundamentals. - Issues · remix-run/remix
GitHub
Nuxt.js should handle "back" swipe gesture by default · Issue #6101...
What problem does this feature solve? I'm unsure if this is a feature request or a bug report: when navigating back with the left swipe gesture on iOS devices, the previous route is re-rendered...
unwilling-turquoise•8mo ago
but there is no fix in any framework?
exotic-emeraldOP•8mo ago
@Manuel Schiller I've never used Nuxt but it looks like Nuxt handled it in the framework (https://github.com/nuxt/nuxt/issues/6101#issuecomment-749400980). I can't say for sure.
Misinformed. I don't think any framework has from my research
unwilling-turquoise•8mo ago
well then it's unlikely we will be the first 😦
exotic-emeraldOP•8mo ago
@Manuel Schiller I understand. NextJS does not have this issue but I'm not even sure how that works under the hood.
@Manuel Schiller Thanks for responding 🙂
unwilling-turquoise•8mo ago
sure thing. if there is an idea how to fix this, we could further investigate. but this looks ... devastating
if you ever come across a potential fix, let us know