-
Notifications
You must be signed in to change notification settings - Fork 680
New issue
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
[12.x] Fix styles overwriting checkout button when class is set #1070
Conversation
To me the behavior I would expect would be to only show these default styles if NO style is passed and NO class is passed by the developer. If either of those things are passed we can't safely add these default styles. /cc @driesvints |
In other words:
|
That makes sense. Updated the commit. |
The way the current PR is shaped would cause the In any case we need to be aware that this is technically a breaking change for anyone using the current behavior. If anyone was either adding styling with the I do agree that the new behavior makes more sense. |
Updated behaviour. Can now do something like:
or
or
If style isset, it'll use custom style, if no class, and no style is set, it'll use default style and If only class isset, will use that. |
In any case in the next major update we'll be able to implement a proper Blade component since we're dropping Laravel 6 support. |
Fixes #1069
If the class is set, the styles would overwrite the class styles, because we're showing default styles because class isset.
Now you can do something like: