Skip to content

v1.8.0 (March 9, 2017)

Choose a tag to compare

View all tags
@louh louh released this 09 Mar 22:57
· 76 commits to master since this release
v1.8.0
34a8c54
  • Added customizable text strings! By popular request, text strings used in the geocoder control can now be customized to your liking. This also enables localisation of the plugin to a different language. For example, check out this geocoder in Korean. (with @hanbyul-here, #120)
  • Deprecated title option! Now that textStrings option is here, the title option is deprecated. It will currently alias to textStrings.RESET_TITLE_ATTRIBUTE, but logs a warning to the console if you use it. The preferred way is to set the textStrings.RESET_TITLE_ATTRIBUTE property directly. (Note: the placeholder option will not be deprecated, since it is frequently used, and remains convenient to keep around. Similarly, it now aliases to textStrings.INPUT_PLACEHOLDER.)
  • You can now force a result to always drop a marker with the overrideBbox option. Previously, a search result would zoom to a bounding box instead of dropping a point marker if bounding box data was available, which made sense for large areas where showing the region was more important than its centroid. However, some people expected point markers to always be dropped. While it was possible to handle selection events yourself and write your own code to always drop markers, we felt that providing the option to do this automatically would be much easier. If the overrideBbox option is true (and markers is not false), selecting a result will always drop a marker, regardless of whether bounding box data is available. #129
  • Results from the venue and address layers will always drop markers. Sometimes, venue and address results come with a bounding box. This meant that markers were not dropped for these small areas, even though a point marker would make more sense. As a quality-of-life improvement we now always drop a point marker for these kinds of results. #129
  • Pressing up / down through a list of results now populates the input with that result's label, which is more in line with user expectations for an autocomplete dropdown (for extra web nerdiness, read the WAI-ARIA Authoring Practices 1.1 Working Draft 17 March 2016 section on auto complete design patterns. #110
  • Added an example to show how you can control the map’s zoom level when a result is selected. #62 (and thanks to @skorasaurus for the help)
  • Added an example to show how you can show region boundary geometry with a secondary request to Who’s on First. #86
  • Improved compatibility with Leaflet v1's Evented object. #150
Assets 2
Loading