We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
filament/filament
Latest (v3)
v10.x
PHP 8.1.x
Using form builder,1, when a form is submitted and submit button is in loading state, disabled=true is set but disabled styling is not applied.
disabled=true
The disabled button, when in the loading state, will have both the default cursor style and the opacity associated with a disabled button:
disabled
filament/packages/support/resources/views/components/button/index.blade.php
Line 55 in ee26b8f
Using form builder, build a form, submit it with the button in loading state, and take a look!
https://github.com/filamentphp/demo
No response
And possibly in other instances, this is only where we encountered it. ↩
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Package
filament/filament
Package Version
Latest (v3)
Laravel Version
v10.x
Livewire Version
Latest (v3)
PHP Version
PHP 8.1.x
Problem description
Using form builder,1, when a form is submitted and submit button is in loading state,
disabled=true
is set but disabled styling is not applied.Expected behavior
The
disabled
button, when in the loading state, will have both the default cursor style and the opacity associated with a disabled button:filament/packages/support/resources/views/components/button/index.blade.php
Line 55 in ee26b8f
Steps to reproduce
Using form builder, build a form, submit it with the button in loading state, and take a look!
Reproduction repository (issue will be closed if this is not valid)
https://github.com/filamentphp/demo
Relevant log output
No response
Donate 💰 to fund this issue
Footnotes
And possibly in other instances, this is only where we encountered it. ↩
The text was updated successfully, but these errors were encountered: