Order of providers for suggested results is now consistently in the same order as providers were optionally configured. This PR also includes related misc. improvements to the suggest UI. #223
v2.2.14
5 years ago
Fixed
Handle attempts to scroll on mobile devices appropriately. (🙏pmacMaps🙏 #215)
v2.2.13
6 years ago
Fixed
Ensure results are filtered using country codes when World Geocoding service is used to fetch an address not based on a suggestion.
v2.2.12
6 years ago
Changed
another guess to ensure all built files make it onto npm
v2.2.9
6 years ago
Changed
exclusively use ES6 imports internally.
run unit tests on Chrome instead of PhantomJS
v2.2.8
6 years ago
/img folder was missing in last npm release
found fix to ensure we no longer have rogue missing files (hopefuly)
v2.2.6
6 years ago
Fixed
esri-leaflet-geocoder.js file was missing in last npm release
v2.2.5
6 years ago
Changed
stop including L.Mixin.Events #180
Fixed
ensure custom geocoding param names are fetched/used when suggestion support is present #182
ensure magicKeys are passed through to custom geocoding services #182
ensure tests don't new up their objects
v2.2.4
7 years ago
Fixed
minor CSS issue on browsers that support touch
the findAddressCandidates operation of geocoding services is now used exclusively, rather than alternating back and forth with find
geocode and search requests are no longer fired when enter is pressed without supplying input text
v2.2.3
7 years ago
Fixed
geosearch control display size is now appropriate in browsers that support touch input (like Chrome 55+ and IE11/Edge)
Correct results are now returned when a featureLayerProvider search is instantiated after executing a previous search that failed to return a single candidate.
a solid gray line is no longer displayed underneath the geosearch control when no candidates were returned by a service.
display text is now aligned correctly on devices that support touch input