Using ->native(false) destroys the appearance of the select
Hello,
Since updating to Filament v4, I've been having a problem with my selects using
->native(false)
See screenshot.
Thanks for your help!
Solution:Jump to solution
I did a clean install and reinstalled each package one by one to identify the error.
The problem comes from the “saade/filament-autograph” package: “^4.0,” which generates unnecessary CSS that interferes with Tailwind...
Here is the code that is causing the problem:...
20 Replies
looks ok on my end
Filament version
v4.0.1

any console errors?
No. I do not have any errors... It's strange that only the select has this problem.
try to run
php artisan filament:assets
That doesn't solve the problem. I had created a custom theme in Filament v3.
Could that be the problem?
resources/css/filament/admin/theme.css
vite.config.js
looks ok. Any css customization that could override the select css?
Did you publish views?
No I commented the css to be sure and I did not published any views.
php artisan filament:about
what is the output?you have views published. Not sure if it is the issue, but you could remove it temporarily and try it again
Only a notification view. I just deleted it. Same bug
create a simple page
php artisan make:filament-page TestPage
Add this code:
let me know if it worksExactly the same error.

some issue related to your project I think
just to confirm: did you run
npm run dev
or build, right?Yes!
Probably. But I followed your update guide to the letter. So others will surely encounter the same problem.
you could create a minimal repo on github, using your project, just to reproduce the issue. I can take a look at this if you want
Thanks. I'll try to do that.
Solution
I did a clean install and reinstalled each package one by one to identify the error.
The problem comes from the “saade/filament-autograph” package: “^4.0,” which generates unnecessary CSS that interferes with Tailwind...
Here is the code that is causing the problem:
Do you know if there is a clean way to prevent the file from being created or loaded?
Thanks!
maybe you could open an issue in the plugin github
Thank you for your help. Sorry for the wasted time.