How to change input type from "text" to "search"

The patch worked fine but some functionality like autosubmit doesn't work as expected. I think need more work with the patch.

While @hudri is correct that there isn't really any semantic or styling benefit to using a <input type="search">, there is one notable UX improvement: every mobile keyboard (to my knowledge) will show a search key instead of enter, and may do other things when it knows it's a search field. It's a minor change, but does add to the overall experience:

1. <input type="search"> on MDN
2. HTML5 Input Types: Where Are They Now? — Smashing Magazine
3. Invoking Search Button in Keyboard While Typing in EditText in Android - GeeksforGeeks - contains a screenshot showing the difference

Created issue fork and made the same change the patch makes but updated to the latest as the patch no longer applies correctly. If you need the updated patch, download the plain diff from GitLab.

I have created a new patch. In conjunction with the patch: 3228546-4-search_type_form_element.patch → from this thread: Allow "search" form element for Views search fields, too → , everything works correctly, i.e. Input has type = 'search', autocomplete works as expected.

> it f... up every design due different user agent style sheets. This is something that everybody has to fix in every project.

Things have maybe changed since that comment 4 years ago.

I've tried this fix on both core's Olivero theme and my project's theme, and I can't see any difference visually.

Using type=search is important for accessibility, as assistive technologies will know to present the form element differently. See https://www.magentaa11y.com/checklist-web/search/ for instance.

Just noticed the MR has a @see to this issue.
I'm removing this -- @see to an issue is not necessary, there is git blame for that. @see to a URL should be used where there's a need to link to something like an external technical document.