fix(searchbar): update alignment of chips and other elements in toolbar #19596
Conversation
This file contains 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
anagstef
reviewed
Oct 16, 2019
| // ----------------------------------------- | ||
|
|
||
| :host-context(ion-toolbar) { | ||
| @include padding(1px, null, 15px, null); |
There was a problem hiding this comment.
@brandyscarney Hello! Is this supposed to be 1px for the top padding? Because updating to this version broke all our searchbars in toolbars. If I change it to 15px it works fine as before.
There was a problem hiding this comment.
Yes, please see my comment here: #19502 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build) was run locally and any changes were pushednpm run lint) has passed locally and any fixes were made for failuresPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: fixes #19495 fixes #19502
What is the new behavior?
!importantDoes this introduce a breaking change?
Other information