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
health men, just my opinion I think the class names for button style outline in v4, it should be following
... class="btn btn-outline-primary" ... ... class="btn btn-outline-secondary" ... ... class="btn btn-outline-success" ... ... class="btn btn-outline-warning" ... ... class="btn btn-outline-danger" ...
instead of
... class="btn btn-primary-outline" ... ... class="btn btn-secondary-outline" ... ... class="btn btn-success-outline" ... ... class="btn btn-warning-outline" ... ... class="btn btn-danger-outline" ...
that is not only a clearer, but can be used for example, another modification as
[class^='btn-outline-'], [class*=' btn-outline-'] { ... }
which is not possible now
The text was updated successfully, but these errors were encountered:
that is not only a clearer, but can be used for example, another modification as [class^='btn-outline-'], [class*=' btn-outline-'] { ... }
I believe we're trying to avoid those sorts of selectors for performance and extensibility reasons.
Sorry, something went wrong.
fixes #17719: rename .btn-*-outline to .btn-outline-*
0be0a8e
Changed in #18772.
Document migration of outline button class in v4
19a012f
See twbs#17719
No branches or pull requests
health men, just my opinion
I think the class names for button style outline in v4, it should be following
instead of
that is not only a clearer, but can be used for example, another modification as
which is not possible now
The text was updated successfully, but these errors were encountered: