-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
Fix the search field height in the back end #1875
Merged
Merged
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
leofeyer
commented
Jun 25, 2020
Comment on lines
+306
to
+309
input[type="search"] { | ||
padding-top:1px; | ||
padding-bottom:1px; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fritzmg
approved these changes
Jun 25, 2020
leofeyer
pushed a commit
that referenced
this pull request
Jun 29, 2020
Description ----------- This is a follow up to #1823, #1875 and #1877 Some previous changes have been reverted, some new changes have been added. * Text inputs and selects and submit buttons now have the same height (and they are aligned correctly). * Layout does not break for certain `w50` widget combinations in any browser, zoom level and dppx combination that I have tested (tested with newest Firefox, Chrome and Edge). @leofeyer can you test these changes in Safari too please? Hopefully this is now fixed for good and we don't have to touch it again, until we re-do the whole thing with CSS grids π If everything checks out, I'll update the PR for Contao 4.4 accordingly. Commits ------- 34cd111 revert some changes from #1823 8f2f282 change the back end layout yet again 7e492ab add minified basic.css 6dd338c some further adjustments for firefox
leofeyer
pushed a commit
to contao/core-bundle
that referenced
this pull request
Jun 29, 2020
Description ----------- This is a follow up to contao/contao#1823, contao/contao#1875 and contao/contao#1877 Some previous changes have been reverted, some new changes have been added. * Text inputs and selects and submit buttons now have the same height (and they are aligned correctly). * Layout does not break for certain `w50` widget combinations in any browser, zoom level and dppx combination that I have tested (tested with newest Firefox, Chrome and Edge). @leofeyer can you test these changes in Safari too please? Hopefully this is now fixed for good and we don't have to touch it again, until we re-do the whole thing with CSS grids π If everything checks out, I'll update the PR for Contao 4.4 accordingly. Commits ------- 34cd1115 revert some changes from #1823 8f2f282a change the back end layout yet again 7e492abf add minified basic.css 6dd338c4 some further adjustments for firefox
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.
This is a follow-up PR to #1823. It seems that the browsers do not like the
height: 30px
for search fields. π€·ββοΈWith the fix from this PR
@fritzmg Can you please check if this applies to the Windows browsers as well?