Can anyone help me why does the search button is necessary in this autosugggest design?
Here is a design that shows the search result when user types the keyword in the input field and can submit the search with enter key from the keyboard. But in the design here is the search button also which seems like it does not do any anything can anyone have some arguments on why we need this search button?
9 Replies
It visually indicates that it is a search field, and some people don't know that you can press enter to submit forms
also, to submit an html form (which this should be, and not just a raw input field) with enter, you have to have a submit button in there. And you should have a page behind it that displays the search results on a POST submission on that form, in case javascript fails or isn't available
So, does not the enter key work the same when the input is a search field? Because lately i had a discussion with devs that the search button is pretty much useless when enter is there to submit the search query. Also, this pattern with teh search button is only in web but in iOS mobile apps it is without the search button.
you can implement an event listener on an input that responds to enter, but afaik you need the submit button in a <form> for it to work out of the box without JS.
and on mobile, UI conventions are different. Not to mention that search boxes often still have a 🔍 in them, even if they aren't buttons
affordance
that's what jochem described, but in 1 word
and yes, you need to put the button in a form
So, does not the enter key work the same when the input is a search field? Because lately i had a discussion with devs that the search button is pretty much useless when enter is there to submit the search query.this is a very bad take have you tried to submit a form in a touch screen device? touchscreen keyboards struggle with this seemingly easy task, specially on linux using the button is, sometimes, the better option
Thank you for the insights. I really appreciate it.Now in the web there is all search with autosuggest or autocomplete are built without search button for example this one. I wanted to have the search button but the dev was arguing that the enter key is enough and no need to have the search button that is the reason i wanted ask people who have been working heavily with UX.
You need at least the 🔎 in there
It doesn't have to be a button if auto suggest works well enough, but I'd still recommend it so that it's more accessible and works without js
same
i have nothing to add, and recommend the same
remember: until the javascript downloads, the browser doesn't have javascript, but everything is still interactive
Thanks 🙂 @ἔρως & @Jochem really appreciate your input and it helps me to give some arguments to the devs who says they don't need the search button!
you're welcome
those devs are scary