[Bug]: Quick Enter key selects wrong item

[sicwere]

Bug description

If you enter text into a Tom Select control, then press the Enter key before the dropdown has been filtered, the wrong item will be selected.

Expected behavior

Entering text into a Tom Select control, then pressing Enter, should always perform filtering correctly, regardless of how fast the Enter key is pressed.

Steps to reproduce

1. Go to https://tom-select.js.org/examples/
2. Scroll to the final dropdown
3. Clear out California and Wyoming from the combobox
4. Type the letter c
5. Press Enter quickly, before the dropdown has been filtered
6. Alabama will be added to the combobox

Additional context

• OS: [Windows]
• Browser [chrome, firefox, edge]

Although the example given uses a select multiple, this bug also occurs in dropdowns where only a single option can be chosen.

[github-actions]

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

[LiiKaz]

I have the same problem (in create=true mode).
Is there any solution ?
I tried setting create and addPrecedence options to true, but if I press enter to quickly it's still the first element that is selected and not the entered text.

[xJuvi]

Hey,
it's not a Bug, it's a feature:

tom-select/src/tom-select.ts

Lines 1578 to 1600 in 4522c18

	// activate
	self.hasOptions = results.items.length > 0 || has_create_option;
	if( show_dropdown ){
	if (results.items.length > 0) {
	if( !active_option && self.settings.mode === 'single' && self.items[0] != undefined ){
	active_option = self.getOption(self.items[0]);
	}
	if( !dropdown_content.contains(active_option) ){
	let active_index = 0;
	if( create && !self.settings.addPrecedence ){
	active_index = 1;
	}
	active_option = self.selectable()[active_index] as HTMLElement;
	}
	}else if( create ){
	active_option = create;
	}

Here you can see, the create "active" marker is only set when not other options are available.

Kind regards

[LiiKaz]

Hey, it's not a Bug, it's a feature:
[...]
Here you can see, the create "active" marker is only set when not other options are available.

Thanks for your reply,

I understand, but the same issue occurs even when no option is available.
If I press Enter too quickly, the first element is always selected instead of the one matching the entered text (or the entered text itself if there is no match).
This seems to be a timing issue: the validation is triggered before the item list is fully loaded.

Is there a workaround for this issue?

Thanks