Back/forward browser cache results in an incorrect null error for unhydrated inputs

[johnbacon]

Package

filament/filament

Package Version

v3.x – Filament Demo site

Laravel Version

Whatever is used in the Filament Demo site as of today

Livewire Version

v3.x – Filament Demo site

PHP Version

Whatever is used in the Filament Demo site as of today

Problem description

See the following for a video demonstration of the issue on Filament's demo site: app.birdeatsbug.com/vmq0tUZ66zl2wkfJydzNXVUP3kI-pnGC-bxe2Uqua1ES

Navigating away from, and back/forward via the browser to, a Filament form does not rehydrate the form fields in question, resulting in an unexpected null error for said input, even when the browser has a non-null value for the form field.

Expected behavior

Expected that the submission of the form would reflect the visual state of the form fields.

Steps to reproduce

See the following for a video demonstration of the issue on Filament's demo site: app.birdeatsbug.com/vmq0tUZ66zl2wkfJydzNXVUP3kI-pnGC-bxe2Uqua1ES

This appears to be because the form fields are not rehydrated on browser back/forward cache.

Reproduction repository (issue will be closed if this is not valid)

https://github.com/johnbacon/demo

Relevant log output

[danharrin]

Have you experienced this behaviour within other Livewire apps before, where wire:model input binding is used? Or is it just Filament?

[johnbacon]

Have you experienced this behaviour within other Livewire apps before, where wire:model input binding is used? Or is it just Filament?

At this point I believe it's simply "the way Livewire works" and therefore a problem with that framework. Since writing this issue, we've found similar mentions in Livewire's own issues + discussion.

Part of the hope now is that increased visibility may spur them/us as a community to solve it in some way.