'No matches found' tooltip persists even after inputting item in combobox

[sktguha]

In combobox, the 'no matches found' tooltip is not cleared after the user has inputted the input after pressing enter.

Steps to reproduce:

Go to https://react.lightningdesignsystem.com/components/comboboxes/
then go to examples: 'Inline Single Selection'
and replace the code in code editor with the below code

https://gist.github.com/sktguha/55f1f78d0b29375ea52ff4436384bee5

if you enter any input and press enter, the tooltip 'No matches found' still persists, as shown in the image below.

[welcome]

Thanks for opening your first issue! 👋
If you have found this library helpful, please star it. A maintainer will try to respond within 7 days. If you haven’t heard anything by then, please bump this thread.

[sktguha]

hi, any update? Currently, I am working around it by calling .focus on the next focussable element, which triggers the onblur thus hiding the tooltip, but it will be good if there is a permanent solution for this.

[garygong]

Thanks for opening the issue! Unfortunately, there is no team dedicated to fixing issues in this project, so it may take some time to get to get around to this. If you already have an idea for how to fix it, feel free to open a PR with the fix. Thanks again!

[sktguha]

Hi @garygong thanks for the response. so basically I have solved it currently by

Currently, I am working around it by calling .focus on the next focussable element, which triggers the onblur thus hiding the tooltip,

[rlodina]

Unfortunately, there is no team dedicated to fixing issues in this project

It is an abandoned project ?

[garygong]

I wouldn't say it's abandoned. We still review PRs and create new releases, but rely on others to submit bug fixes.

[stale]

This issue has been automatically marked as stale, because it has not had recent activity. It will be closed if no further activity occurs. Maintainers are responsible for tech debt and project health. This is most likely a new components or component feature request. Please submit a pull request for or request feedback on this feature. Thank you.

[lawteo]

The behaviour that @sktguha mentioned is due to the check for menuOptions.length in combobox. Here is the snippet

{menuOptions.length ? (
		menuOptions
	) : (
		<li
			className="slds-listbox__item slds-listbox__status"
			role="status"
			aria-live="polite"
		>
			<span className="slds-m-left_x-large slds-p-vertical_medium">
				{props.labels.noOptionsFound}
			</span>
		</li>
	)}

Is there a use case where the options list is empty?
If the list is not empty, entering giberish leaves the entire option list showing indicating that there is no match. This seems to be a correct behaviour as the user is expected to select from one of the options. Right?

[stale]

This issue has been automatically marked as stale, because it has not had recent activity. It will be closed if no further activity occurs. Maintainers are responsible for tech debt and project health. This is most likely a new components or component feature request. Please submit a pull request for or request feedback on this feature. Thank you.