-
Notifications
You must be signed in to change notification settings - Fork 19
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
Geocoder input does not get focus upon opening #182
Comments
Thanks for taking the time to open this issue! |
I think the problem is that the collapse mode is quite unusual - most UIs, e.g. Google Maps, have an always-visible control. As a result there is no ambiguity in that scenario. Here, the user is actually interacting by hovering on the icon, and so it feels odd to have then to select a second time, this time with a click. On the other hand, I accept your point that an accidental hover then leaves the box upon. To me the lack of autofocus feels more problematic.
At the very least, if the user has actually clicked on the search icon, that is a clear indication of search - at present they still then have to click on the search input. |
Can you link to a video or a place to better explain the issue, I might not fully understand the problem... |
Reproduce case:
It seems unnecessary for the user to have to then click - the act of hovering over the control is more likely than not to indicate that they want to do a search. My suggestion would be an |
Currently, when the widget is added to the map, and the user hovers over the search button, the input field is uncollapsed, but the user has to give focus manually by clicking in the input field. This seems unnecessary, given that the user intention will almost always be to want to start typing.
It would therefore be useful to have a focus/autofocus option to add autofocus.
For now, the following workaround will do this:
The text was updated successfully, but these errors were encountered: