For comparison, using Chrome in Android it works properly.

This is how I'm currently working around this, in my load method:

	let dropdown = document.getElementById('global-search-ts-dropdown');

	if (query != last_query) {
		last_scroll_position = 0;
	} else if (dropdown) {
		last_scroll_position = dropdown.scrollTop;
	}

	last_query = query;

Then I do all my ajax loading. After I've executed the callback, I set the scrollTop again:

callback(res.list);
dropdown.scrollTop = last_scroll_position;

This issue has not been active in 120 days and has been marked "stale". Remove stale label or comment or this will be closed in 15 days

This is still an issue in version 2.3.4

The workaround that I currently use monkeypatches scrollToOption to not do anything until the callback has done its thing.

      fetch(url)
        .then(response => response.json())
        .then(json => {
          const _scrollToOption = this.scrollToOption
          this.scrollToOption = () => {}
          callback(json.results)
          this.scrollToOption = _scrollToOption

No news about this issue?

Tracked this one down to same_query in refreshOptions: when it is called following new options being added its value almost always is false, which is wrong since the query didn’t change. The result is that the first option is considered the active one, and scrolled to.

@skerit can you share your solution, please?
Thanks