filamentphp / filament

A collection of beautiful full-stack components for Laravel. The perfect starting point for your next app. Using Livewire, Alpine.js and Tailwind CSS.
https://filamentphp.com
MIT License
18.07k stars 2.83k forks source link

isIndividual searchable field lose focus after lazy load #7767

Closed hsul4n closed 1 year ago

hsul4n commented 1 year ago

Package

filament/tables

Package Version

v3.0.14.0

Laravel Version

v10

Livewire Version

v3

PHP Version

PHP 8.2

Problem description

When start typing on individual search table column after finish writing the focus is lost and I should press on the field again to finish writing and when no result found the field is disappeared and not showing anymore unless clear filters again.

Expected behavior

Steps to reproduce

Reproduction repository

https://github.com/hsul4n/filamentphp-demo

Relevant log output

No response

github-actions[bot] commented 1 year ago

Hey @hsul4n! We're sorry to hear that you've hit this issue. 💛

However, it looks like you forgot to fill in the reproduction repository URL. Can you edit your original post and then we'll look at your issue?

We need a public GitHub repository which contains a Laravel app with the minimal amount of Filament code to reproduce the problem. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private / confidential, since we want a link to a separate, isolated reproduction. That would allow us to download it and review your bug much easier, so it can be fixed quicker. Please make sure to include a database seeder with everything we need to set the app up quickly.

github-actions[bot] commented 1 year ago

Thank you for providing reproduction steps! Reopening the issue now.

sakanjo commented 1 year ago

The same happens with me, plus the search filters are not saved

Waiting for a confirm from the assignees so i can start working on it

danharrin commented 1 year ago

Doesn't appear to be a problem in the latest release.