unsavedChangesAlerts() not triggered when reordering a Repeater component #17699
Description
Package
filament/filament
Package Version
v4.0.7
Laravel Version
v12.28.1
Livewire Version
^3.5
PHP Version
PHP 8.4
Problem description
Describe the bug
unsavedChangesAlerts() not triggered when reordering a Repeater component.
See animated Gif as it shows exactly the issue.
Screenshots
ANIMATED GIF
Desktop (please complete the following information):
I'm using Desktop
- OS: Windows 11 (updated)
- GPU: NVIDIA RTX 3050]
- Backend: OpenGL
- Google Chrome (updated to latest version)
- Laravel stable 12.28.1
- Filament stable 4.0.7
- Livewire ^3.5 (default with filament)
- PHP 8.4
Additional context
Need more context, just ask, but you'd probably be able to find it in the linked repository.
Expected behavior
Expected behavior
Expecting the warning to pop-up saying that you will lose changes made in the form when leaving the page without saving first.
Steps to reproduce
To Reproduce
Steps to reproduce the behavior:
Using existing code (option 1)
https://github.com/christoferd/filament-bug-demo-2025
- clone, install, setup .env, migrate, seed
- go to Customers resource,
- Edit a Customer
- then follow steps below from step 3.
DIY (option 2)
- add
->unsavedChangesAlerts()to the Panel - go to a Form/Resource Edit that contains a Repeater component
- make sure there are at least 2 records in the Repeater component
- save the form, refresh the page
- change the order of the Repeated records, do not save
- click on a navigation link that will take you away from the page (expecting the warning to pop-up)
- Notice the issue, that the warning did not popup and the next page loaded, losing the changes made in the edit form.
Reproduction repository (issue will be closed if this is not valid)
https://github.com/christoferd/filament-bug-demo-2025
Relevant log output
**Logs**
I didn't see anything in the Browser Console Log, and there are no Laravel error logs.
If there are logs to produce then let me know.