Drop support for .form-control-plaintext inside .input-group#28972
Merged
Drop support for .form-control-plaintext inside .input-group#28972
Conversation
Member
|
I'd be cautiously in favor of this. |
MartijnCuppens
approved these changes
Jun 27, 2019
|
Why? This is so usefull. I lost minutes trying to solve this. Makes no sense if an input field could have append and prepend, but a readonly input not. 🤷♂️ .input-group > .form-control-plaintext:not(:first-child) {
padding-right: 0.75rem;
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drop support for
.form-control-plaintextinside.input-group, because this cause #28205.Closes #28205