Hi @plakak,

Thanks for the PR.

I think we reset the highlighted option (and scroll) because the current highlighted option may not be available after the filter.

So if highlightedIndex is not reset, it'll highlight a new option that's in the same position after the filter. We also could possibly have a out-of-bounds array access if the highlightedIndex is greater than the number of items after the filter, and the user presses ENTER to select the highlighted item.

We may need to find a way to prevent filteredOptions from re-evaluating to a new array on select, so the scroll doesn't reset.

Hi @JosephusPaye,

After a long debugging session I found the problem. Apparently if one adds object directly in the template like this

 <ui-select
        label="Favourite colours"
        multiple
        :keys="{label: 'label', value: 'value'}"
        :options="colours"
         v-model="select7"
></ui-select>

on each model change vue recreates this object and prop gets updated. I've tested this on a simple component of my own and it happens. If one would get keys from data like :keys="myKeys" than everything is fine.

Since it's really convenient to add keys directly in the template I think the library should walkaround this -compare keys internally and change them only if the value changed and not just reference.
I updated the PR.