Click next or previous page in the AI Search results page does not auto refresh to the top of the page when 'Filters' section of 'Faceted Search' applet is beyond certain size relative to page.DescriptionIf the 'Filters' section of the 'Faceted Search' widget takes up enough vertical height, when navigating between pages of results, the page is not getting returned to the top on each.This can occur for two main reasons.1. Due to the number of entries in the 'Filters' section, controlled by the 'Facet Value Limit' field on the 'sys_search_facet' table, being a high enough value, and there being sufficient results to populate it to increase its vertical height.2. By increasing the zoom on the browser, resulting in the 'Filters' section being larger on the page. Steps to Reproduce: Using an out of box AI Search enabled instance: 1. Create multiple Categories (sc_category), say 20, 'Category 1' to 'Category 20'.2. Copy the 'Apple iPad 3' Catalog Item (sc_cat_item) 20 times, and assign one to each category.3. Alter the value of the 'Facet Value Limit' against the 'Categories' record in the sys_search_facet table to 30.4. Go to Service Portal and search for 'Apple iPad' -> This should result in all the new items being returned, with all new categories showing in the 'Filters' section.5. Navigate to the next page of results, and then back, via the arrow icons at the bottom of the page. You should find that when you navigate pages it does not return to the top. If it does, increase the zoom of the browser until it then doesn't. Expected behaviour: The page should take the user back to the top of the page.Actual behaviour: The page bounces back to the bottom of the page when the 'Filters' section extends vertically enoughRelease or EnvironmentAI Enabled instancesCausePRB1540895: Marked as fixed in Tokyo. No back ported fix is available.ResolutionPRB1540895 is marked as being fixed in the Tokyo release. Otherwise, possible workarounds available are: 1. To reduce the number of entries in the 'Filters' section of the 'Faceted Search' applet, by way of the 'Facet Value Limit' field set on the 'sys_search_facet' table. 2. Make the following alterations to the 'Faceted Search' widget, BUT make sure to revert (and re-apply) these changes before/after any future patch/upgrades. Or, alternatively, you can clone the widget and make these changes. CHANGE 1 :a) Search the client controller script for the line: $scope.results = searchResults b) Add this line after it: $scope.$emit('$scrollToResultsTop'); CHANGE 2:a) Search the client controller script for the line: case PAGINATION_BUTTON_CLICKED: b) Add the following line before the break statement of the above case statement: $scope.$emit('$scrollToResultsTop'); The resultant snippet should look like the following ------------------------------------------------------------------------case PAGINATION_BUTTON_CLICKED:inputConfig.paginationToken.value = e.detail.payload.paginationToken;spAISearchResults.locationSearch(angular.extend($location.$$search, {spa: '1',paginationToken: inputConfig.paginationToken.value || undefined}));$scope.$emit('$scrollToResultsTop'); //NEW LINE ADDED HERREbreak;----------------------------------------------------------------------- CHANGE 3:a) Search for the following string in the client script - if (!c.data.aisEnabled) { b) Add the following snippet above it: -----------------------------------------------------------------------$scope.$on('$scrollToResultsTop', scrollToResultsTop);function scrollToResultsTop() {var scrollableSection = $('.sp-scroll');if (scrollableSection.length)scrollableSection[0].scrollTo(0,0);}-----------------------------------------------------------------------