Safari-specific navigation issue: URL changes but page doesn't update

Issues
1

Hi Plasmic team,

I’m encountering a browser-specific navigation issue in my Plasmic site. When clicking navigation links in Safari, the URL changes correctly but the page content doesn’t update. This same navigation works perfectly in Chrome.

Key details:

  • Issue occurs consistently across multiple Safari browsers on different computers
  • URL changes correctly when clicking links
  • Network tab shows the fetch request completing successfully
  • No console errors appear in Safari’s Web Inspector
  • Page content remains static despite URL change
  • Previously fixed a similar issue in Chrome by removing transition bindings, but Safari issue persists

My Plasmic project URL: [Project]

Any guidance on resolving this Safari-specific navigation issue would be greatly appreciated. Are there any known workarounds or settings I should check?

Thank you!

2

I wanted to share a solution to a tricky Safari-specific navigation issue I encountered and resolved. This might help others facing similar problems.

Issue:

  • In Safari only, clicking navigation links would change the URL but not update the page content
  • This happened specifically after refreshing a page or visiting it twice
  • The site worked normally in Chrome

Root Cause: The problem was traced to a reusable button component that had its disabled state set using Plasmic’s built-in disabled variant. When this disabled state was active, it prevented proper navigation in Safari.

Solution: Instead of using Plasmic’s registered disabled variant, I created a custom variant to replicate the disabled button behavior. This completely resolved the navigation issues while maintaining the desired button functionality.

I hope this helps anyone else who encounters similar Safari navigation problems. If you’re seeing URLs change without page updates in Safari, check for any components using the built-in disabled variant state.

3

As a note, this problem happens anytime I add any customizable component and set it its disabled variant to true. Not sure how to get to the root cause, but avoiding the disabled state or the read only state on these components for now.

4

Actually I have added more customizable components, like select and radio groups with nothing disabled and it is causing the navigation problem again. For now I will avoid reusable components, but would love to figure out what is going wrong here.