With your approach you get full control over the design of the “x”, but it requires JS and you need to use care to make sure it remains accessible.
With <input type=“search” /> you can’t change the look of the “x”, but it will match their OS, which could be desirable! It also won’t require JS to function and should be accessible.
Well, as with everything... it has trade offs.
With your approach you get full control over the design of the “x”, but it requires JS and you need to use care to make sure it remains accessible.
With
<input type=“search” />you can’t change the look of the “x”, but it will match their OS, which could be desirable! It also won’t require JS to function and should be accessible.I updated my code 😃