Hey all,
I'm running into an issue with Chrome on iOS where the back button either skips multiple pages or jumps to the previous domain. This is a huge deal, especially in scenarios like a single-page application (SPA), where each step in the flow is crucial for conversion. Losing that precise navigation can really hurt the user experience.
Has anyone else come across this? Any fixes or workarounds would be really helpful.
Thanks in advance!
Steve
--
You received this message because you are subscribed to the Google Groups "navigation-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to navigation-de...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/navigation-dev/8d44b952-441f-4531-b45a-f9651cb0bfeen%40chromium.org.
@Ali Juma : Thanks for the context! Is there a bug/document mentioning webkit's skipping behavior? Mostly curious to see how similar/different it is with chromium's behavior. Thanks!On Fri, Oct 4, 2024 at 10:15 AM Ali Juma <aj...@google.com> wrote:In Chrome on iOS, this behavior (of skipping over items added without user interaction) is enabled on iOS 17.5+ in Chrome 127+.WebKit looks at whether there was user interaction within the past 10 seconds, *and* that this interaction has not already been "consumed" by certain APIs.https://webkit.org/blog/13862/the-user-activation-api/ is a good reference for these concepts, explaining what counts as user interaction, and which APIs can "consume" a user interaction.
--Shivani
In Chrome on iOS, this behavior (of skipping over items added without user interaction) is enabled on iOS 17.5+ in Chrome 127+.WebKit looks at whether there was user interaction within the past 10 seconds, *and* that this interaction has not already been "consumed" by certain APIs.https://webkit.org/blog/13862/the-user-activation-api/ is a good reference for these concepts, explaining what counts as user interaction, and which APIs can "consume" a user interaction.
On Fri, Oct 4, 2024 at 3:12 AM Steve Rehm <cremed...@googlemail.com> wrote: