You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clicking anywhere in the search box, not just on the search icon, will collapse the search box with default settings. This is an issue, as actions such as deselecting text and clicking to reposition within it that should not blur the input field are collapsing it.
Reproducing
I could reproduce this bug on Chromium v66 and Firefox v61, with leaflet-control-geocoder v1.5.8. Notably, I could not reproduce the issue with leaflet-control-geocoder v1.5.7.
Clone the gh-pages demo and put leaflet v1.3.1 and leaflet-control-geocoder v1.5.8 in place
Click in the search box and type anything
Click anywhere on anything you have just typed
The search box collapses; it should not
Further Pointers
The issue appeared to be that mouse/pointer/touch events were reaching the outer control container instead of the inner input element. Adding an event.preventPropagation() to the inner <input> tag appeared to mitigate the issue on some level.
The text was updated successfully, but these errors were encountered:
Problem
Clicking anywhere in the search box, not just on the search icon, will collapse the search box with default settings. This is an issue, as actions such as deselecting text and clicking to reposition within it that should not blur the input field are collapsing it.
Reproducing
I could reproduce this bug on
Chromium v66
andFirefox v61
, withleaflet-control-geocoder v1.5.8
. Notably, I could not reproduce the issue withleaflet-control-geocoder v1.5.7
.gh-pages
demo and putleaflet v1.3.1
andleaflet-control-geocoder v1.5.8
in placeFurther Pointers
The issue appeared to be that mouse/pointer/touch events were reaching the outer control container instead of the inner input element. Adding an
event.preventPropagation()
to the inner<input>
tag appeared to mitigate the issue on some level.The text was updated successfully, but these errors were encountered: