No dirty state warning when using browser back button

[helloDanuk]

Bug description

The following has already happened to me a few times: Editing an entry on my MacBook Pro and using my Trackpad to scroll up and down while editing an entry deletes my unsaved changes without warning.

If my finger movements do not clearly move up and down, but rather left/right, the browser changes back and forth without warning of unsaved changes. Results in data loss.

This happen also then using the browsers back and forth buttons.

• Tested in Chrome
• Warning in Preferences is enabled

How to reproduce

Bildschirmaufnahme.2026-02-24.um.15.13.27.mov

Logs

Environment

Environment
Application Name: Statamic
Laravel Version: 12.52.0
PHP Version: 8.3.30
Composer Version: 2.9.3
Environment: local
Debug Mode: ENABLED
URL: six-test.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 0
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.3.3 PRO

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[vitalijalbu]

why don't using thr disabled button isDiry inertia?

[duncanmcclean]

That's not the problem. We need to override the browser's back/forward navigation events which is harder than it seems. We already handle Inertia navigation events.