Filament v3 table pagination state under concurrent Livewire requests

Filament v3 tables paginate through Laravel’s paginator and expose page size through recordsPerPage(), defaulting to 15 records. Page, sort, and filter state live as Livewire component properties persisted to the session.

When the same table is open in multiple browser tabs, or rapid concurrent requests target one component, those session-backed properties can be overwritten instead of isolated per request. It is unclear whether this shared state is intentional or whether it produces stale rows, missing pages, or apparent latency.

Assumptions: Filament v3.x, default Livewire session persistence, and no custom middleware altering pagination state. Filament v2 behavior may differ and should not be assumed.

Questions:

• Does Filament intend table pagination state to be shared across tabs for one authenticated session?
• Can concurrent Livewire requests overwrite page, sort, or recordsPerPage values and return stale or missing rows?
• Is there a supported way to scope pagination state per browser tab while retaining server-side pagination?