[BUG] Back navigation from /editor skips or freezes homepage

[krishx06]

Describe the bug:
When navigating between the homepage (/) and the editor (/editor), the browser’s Back button behaves inconsistently.
Sometimes it:

1. Skips the homepage entirely and jumps back to the previous external page (like a Google search),
2. Does nothing and stays stuck on /editor, or
3. Requires multiple back presses to reach the homepage, and then forward navigation skips it again.

This makes navigation within the app unpredictable.

Steps to reproduce the behavior:

1. Search for “drawdb app” on Google.
2. Click the first link → opens the homepage (https://www.drawdb.app).
3. Click “Open Editor” to go to /editor.
4. Press the browser Back arrow (←).

Observe one of the following:

1. Homepage skipped → returns directly to Google.
2. Back button unresponsive.
3. Multiple presses required to reach homepage, and forward skips it again.

Expected behavior:
Pressing Back from /editor should always return to the homepage (/) before leaving the site.
Pressing Forward should go through the same in-app routes (homepage → editor) in order, without skipping.

Screenshot / Screen Recording
A short screen recording demonstrating all three navigation issues is attached below.

Screen.Recording.2025-11-10.at.9.39.22.AM.2.mov

Desktop:
OS: macOS
Browser: Google Chrome (latest)
Reproducible: Yes (both normal and incognito mode)

[krishx06]

Hey! I’d like to work on fixing this issue.

I’ve already reproduced the bug and believe it’s related to inconsistent handling of browser history between the homepage (/) and the editor (/editor).

Please assign this issue to me, as I’ve already started working on a fix and will open a PR soon.

[krishx06]

Update:

I’ve been testing this further and observed the following:

• Before adding a table: Navigation between / and /editor works normally.
• After adding a table: The browser Back button becomes unresponsive or requires multiple clicks to leave /editor, sometimes getting completely stuck.

This behavior is consistent on both localhost and the official hosted website.
I’m continuing to investigate the exact cause and have a lead on where it might be originating.
Open to any suggestions or guidance from the team while I work on this @1ilit .