Fix: Back navigation freezing on /editor after adding tables (#687) #692
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #687
Summary:
Fixes the issue where the browser’s Back button freezes or skips pages after adding a table in the /editor view.
Problem:
save()inWorkspace.jsx, which always callssetSearchParams(searchParams);even when no URL changes are needed./editorentry to browser history on every save, causing the Back button to become unresponsive or require multiple presses.Solution:
setSearchParams()when shareId exists in the URL.{ replace: true }to replace the current history entry instead of pushing new ones.Result:
Verification:
Screen.Recording.2025-11-12.at.12.51.06.AM.2.MOV
Notes:
This PR makes a minimal, targeted change to fix the root cause without affecting other functionality or state handling.