July 2019 Release (v2.6459)
This page summarizes the improvements, new features, and bug fixes introduced in the July 2019 Release (initially released as v2.6459.4).
To download the latest version of this release (v2.6459.11):
- From Github: 2.6459.11 release on GitHub.
- From npm:
npm install email@example.com
- From a CDN:
|Resource||Script to include|
For more available resources, see CDN Links.
New Component: MissingTerms
Issue number: JSUI-2454
MissingTerms result template component renders a list of query terms that were not matched by a given result item. This component is now included in the default result templates.
By default, the component allows the end user to click any missing term to filter out items that don’t match this term (see the
New Analytics Feature: Push Events to Google Tag Manager Data Layer
Issue number: JSUI-2467
Analytics component can now be configured to automatically push usage analytics events to a properly initialized Google Tag Manager data layer object.
New Searchbox Option: height
Issue number: JSUI-2349
New Omnibox Option: querySuggestCharacterThreshold
Issue number: JSUI-2458
querySuggestCharacterThreshold option of the
Omnibox component allows you to specify the minimum number of characters required in the search input before displaying available query suggestions when focus is on the component.
For example, by setting this option to
1, you can ensure that no query suggestions are displayed when the search box is empty.
New SimpleFilter Option: sortCriteria
Issue number: JSUI-2401
sortCriteria option of the
SimpleFilter component allows you to specify whether to sort values in a given simple filter by ranking score (default), alphanumerically, by number of occurrences, or using the chi-square test.
New ResultList Option: enableScrollToTop
Issue number: JSUI-2413
enableScrollToTop option of the
ResultList component allows you to specify whether to automatically scroll back to the top of the page when infinite scroll is enabled (see the
enableInfiniteScroll option) and the end user interacts with a facet.
The option is set to
true by default. Setting it to
false would yield a behavior similar to what follows:
Improved Pilot Component: DynamicFacet
Issue numbers: JSUI-2442, JSUI-2482, JSUI-2513, JSUI-2397
DynamicFacet component has been improved in several ways:
Automatic padding has been added to dynamic facets so they no longer move around when the end user is interacting with them.
FieldValueresult template component is now compatible with dynamic facets.
Dynamic facets can now be used alongside certain non-dynamic facet components, though some limitations still apply (see Using Dynamic Facets Alongside Non-Dynamic Facets).
|Issue number||Case||Maintenance case|
|JSUI-2320 / JSUI-2507||00047446 / 00054093||Fixed accessibility issues.|
|JSUI-2488||00053573||Fixed issue with default date format.|
|Issue number||Bug fix|
|JSUI-2376||[Accessibility] Fixed tab navigation issue with Settings and Search buttons.|
|JSUI-2377||[Accessibility] Fixed issue where space key didn’t activate buttons.|
|JSUI-2394||[Accessibility] Fixed issue where the escape key didn’t close the facet settings menu.|
|JSUI-2460||Fixed issue where certain usage analytics events were not sent when using IOS Safari.|
|JSUI-2465||Fixed error in
|JSUI-2475||Fixed console warning issue in IE11.|
Additional Changes in Maintenance Versions
|JSUI-2581||Support tagging items viewed by user.|
|Issue number||Bug fix|