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
For example a search icon is often added to filter forms:
TBD: in the internet-header, it is used as a button. How to differentiate both? Should we allow icons to be append to input?
The text was updated successfully, but these errors were encountered:
@imagoiq have a look at https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=16739%3A53259&mode=design&t=uFqiwSCwgBx3yCuO-1. This will be the new search field.
Another approach would be adding the generic possibility to add pre- and postfixes to input fields (https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=10657%3A50263&mode=design&t=uFqiwSCwgBx3yCuO-1).
The datepicker is a similar use case.
Sorry, something went wrong.
Design is ready
<input type="search">
No branches or pull requests
For example a search icon is often added to filter forms:
TBD: in the internet-header, it is used as a button. How to differentiate both? Should we allow icons to be append to input?
The text was updated successfully, but these errors were encountered: