v1.3.6

Bug Fixes

• Fixed a bug that prevented text in escaped query suggestions from being properly highlighted.
• Small corrections were made to the README.
• Corrected the back navigation behavior for FilterOptions. (#1080)
• Corrected a back navigation issue for Facets resulting from history getting pushed instead of replaced. (#1064)
• Fixed a bug with the FilterBox component where the URL was getting updated before 'Apply', even when searchOnChange
  was false. (#1014)
• Fixed pagination bugs that occurred on back navigation and page refresh (#1060).

Version 1.6.2

Bug Fixes

• The new VerticalResultsCount component has a new noResults.visible configuration option.
  The option defaults to false. This means that by default, the count does not appear when there are no results. (#1142)
• Updated the SDK to use the minimal-safe distribution of the plural-forms library. This distribution does
  not make use of unsafe-evals. (#1149)
• Fixed a bug that prevented text in escaped query suggestions from being properly highlighted. (#1144)
• Made a couple of small translation corrections. (#1123)
• Corrected the back navigation behavior for FilterOptions. (#1080)
• Corrected a back navigation issue for Facets resulting from history getting pushed instead of replaced. (#1064)

Version 1.6.1

Fixes:

• Fix race condition with DefaultTemplatesLoader (#1125)

Version 1.6.0

Version 1.6.0

Version 1.6.0 introduces new internationalization features including language-specific SDK assets and localized maps. New components include an AppliedFilters component and a VerticalResultsCount component which replace the now-deprecated ResultsHeader component. Other changes include improving WCAG compliance, measuring performance, removing global polyfill pollution, ensuring styling is self-contained, and returning a promise from the Answers init.

Changes

• New SDK bundles are available for French, German, Italian, Spanish, and Japanese. The bundles contain different translations for static strings. The translated bundles are available with the language or locale prepended to the asset name. For example, “de-answers.min.js” and “de-answerstemplates.compiled.min.js” include German translations. Some locales which include regions are also supported, but the translations are no different than the language-specific assets. For example, the asset “es_US-answers.min.js” contains the same translations as “es-answers.min.js”.
• The map component now supports a locale option which determines the language of the map. If a locale option is not supplied, the locale supplied when initializing answers will be used.
• The applied filters and the results count portions of the results header were factored out into the new AppliedFilters component and VerticalResultsCount component. The ResultsHeader component built into VerticalResults is now deprecated. We recommend using these new components instead.
• Answers init returns a promise. Code that was previously inside the onReady callback can be instead called with promise .then() syntax.
• Performance marks are now available in the console with performance.getEntries().
• Non-UMD (IIFE) template bundles are available with the name answerstemplates-iife.compiled.min.js.
• WCAG compliance for autocomplete was improved.
• The value of sessionsOptIn now persists across page navigation.
• A resultsCountByVertical entry was added to onUniversalSearch. For each vertical, there is an object of the form: { totalResultsCount: 150, displayedResultsCount: 10 }. The totalResults count indicates how many results were found for that vertical and the displayedResultsCount indicates how many of those results are actually displayed.
• Global polyfills were removed in order to make the library and template bundle self-contained.

Styling Updates

• All styling in the SDK is now self contained.
• FilterOptions: update styling so that the vertical scrollbar appears when the options exceed the max-height.
• AlternativeVerticals: add :focus styling to links.

Bug Fixes

• Filters/Facets - Do not update the URL until the apply button is pressed.

Version 1.5.5

Fixes:

• Remove unsafe eval usages in a search bar only page (#1062)
• Pagination: Fix disappearing pagination on back nav and refresh (#1060)
• FilterOptions: fix ie11 issue with clearing searchable facets (#1058)

Version 1.4.7

Fixes:

• Remove unsafe eval usages in a search bar only page (#1062)
• FilterOptions: fix ie11 issue with clearing searchable facets (#1058)

v1.5.4

Version 1.5.4

Changes

• We made a fix to the SearchBar's template to ensure the component could be used on a site whose Content Security Policy disallows unsafe-eval. (#1043)
• We changed how the Component class makes a copy of internal state. The previous algorithm clashed with React and effectively prevented the SDK from being used with it. (#1048)

v1.4.6

Version 1.4.6

Changes

• We made a fix to the SearchBar's template to ensure the component could be used on a site whose Content Security Policy disallows unsafe-eval. (#1045)
• Fixed a bug that was pushing a state into the browser history for each Facet on page load. Instead, we correctly replace browser history on load. (#1021)
• Fixed a bug wherein previous results were still displayed if you navigated back to an empty query. (#1022)
• We now pass a replaceHistory parameter to onStateChange callbacks. These callbacks will still be passed the contents of persistentStorage too. This new parameter is needed to indicate if history state was pushed or replaced when persistentStorage was updated. (#1027)

v1.3.5

Version 1.3.5

Changes

• We made a fix to the SearchBar's template to ensure the component could be used on a site whose Content Security Policy disallows unsafe-eval. (#1044)
• Fixed a bug that was pushing a state into the browser history for each Facet on page load. Instead, we correctly replace browser history on load. (#1019)
• Fixed a bug wherein previous results were still displayed if you navigated back to an empty query. (#1022)
• We now pass a replaceHistory parameter to onStateChange callbacks. These callbacks will still be passed the contents of persistentStorage too. This new parameter is needed to indicate if the history state was pushed or replaced when persistentStorage was updated. (#1027)

Version 1.5.3

Changes

• facets/filteroptions: replace state for facets on page load (#1020). When loading a page with facets, a browser history state is no longer pushed for every facet. A history state is only pushed on a change to the facets. This solved a bug where users would get "stuck" after entering a page with facets.
• search: respect back navigation with empty search (#1022). When a user navigates back in browser history to a page without a query, the original state is preserved. That is, the results are hidden and no query is conducted.
• alternativeverticals: update universal URL on context change (#1025). When a user calls ANSWERS.setContext, the universal results link in the AlternativeVerticals component (No Results) is updated to reflected the new context.
• persistentstorage: Add replaceHistory as onStateChange param (#1027). To support implementations hoping to recreate SDK query param behavior, we add replaceHistory information to the onStateChange listener params.