Webflow sync, pageviews & more.
NEW

Does Webflow have a fix for the bug where the previous page does not appear when using the native browser buttons in Safari?

TL;DR
  • Safari issues with Webflow often stem from custom page transitions, unload events, or injected scripts that interfere with the browser's back/forward cache.
  • To mitigate, remove or test without custom navigation scripts, avoid unload handlers, use standard Webflow links, and report unresolved cases to Webflow Support.

Webflow currently does not have a built-in fix for the Safari-specific issue where the browser's Back/Forward buttons fail to show the previous page properly.

This is a known issue tied to certain Webflow setups in Safari, particularly where page transitions or JavaScript-driven content manipulation interferes with Safari's page caching or back/forward navigation behavior.

1. Understand the Issue Context

  • This primarily affects Safari (macOS and iOS) when users navigate using the browser's Back or Forward buttons.
  • It often occurs when using custom page animations, full-page transitions, or AJAX-style navigation within Webflow.
  • The behavior might result in a blank screen, frozen page, or no visual response when navigating backwards.

2. Check for Potential Causes in Your Project

  • Custom Code: Scripts overriding default browser behavior (e.g., custom routing or fullPage.js) can break Safari's back/forward cache (bfcache) support.
  • Page Load Interactions: Complex page load or unload interactions may interfere with Safari’s ability to restore the page state.
  • Embedded Content or DOM Manipulations: Dynamically injected elements (e.g., third-party plugins or popups) can disrupt page restoration.

3. Potential Workarounds

While there is no official Webflow fix, consider these workarounds:

  • Remove or Refactor Page Transition Scripts: If using custom JavaScript for smooth page changes, test your site without them in Safari.
  • Avoid Custom Unload Events: Do not use window.onunload or beforeunload handlers unless absolutely necessary.
  • Use Traditional Link Navigation: Ensure internal links are standard Webflow links rather than handled via custom JS, which can bypass native browser history behavior.
  • Test Without Interactions: Temporarily disable page load interactions to isolate whether they conflict with Safari’s page caching.

4. Report to Webflow Support

  • If your project does not use custom code and you still experience the issue, submit a bug report to Webflow Support with detailed steps to reproduce it in Safari.

Summary

Webflow does not currently provide an official solution for Safari's back/forward button malfunction, especially when custom transitions or scripts are involved. To minimize the issue, limit custom navigation logic, refactor page load interactions, and use standard Webflow links. For persistent issues, report them directly to Webflow.

Rate this answer

Other Webflow Questions