-
Notifications
You must be signed in to change notification settings - Fork 78
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
4989 - search x header alignment fixes #5022
Conversation
Just a note that also in this branch/PR:
|
f6f15a8
to
241e59b
Compare
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.
Great PR with all the docs improvements, thanks for this! Just found one thing below
right: 35px; | ||
top: 4px; | ||
align-items: center; | ||
display: flex; |
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.
I found one Searchfield example where the close button is still displayed when the input has no contents: http://localhost:4000/components/tabs-module/example-category-searchfield-go-button.html -- seems to be tied to this rule? We may have to qualify it somehow with input:empty
or with .is-empty
coming from the wrapper?
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.
Good catch Ed, thanks. Checking into it.
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.
forgot to push there -- just running through CI now
65de6a2
to
6066ff0
Compare
Explain the details for making this change. What existing problem does the pull request solve?
Should solve most (if not all) of the styling issues with the search fields and toolbar search fields that contain clear buttons.
Related github/jira issue (required):
Closes #4989
Steps necessary to review your pull request (required):
Previously the "X" would be down into the search field on certain scenarios; this should no longer happen.
As mentioned in the issue, the components in these sections should be checked locally.
http://localhost:4000/components/searchfield
http://localhost:4000/components/toolbarsearchfield
http://localhost:4000/components/header
http://localhost:4000/components/tabs-module
For reference/sanity check if the PR is merged:
https://master-enterprise.demo.design.infor.com/components/searchfield
https://master-enterprise.demo.design.infor.com/components/toolbarsearchfield
https://master-enterprise.demo.design.infor.com/components/header
https://master-enterprise.demo.design.infor.com/components/tabs-module
Included in this Pull Request: