Replies: 3 comments
-
Good idea. Pondering about it makes me realize that this could be used for tracking user behavior or for analytics too. Will launch a PR with the necessary updates soon. Thanks for the idea. |
Beta Was this translation helpful? Give feedback.
-
Hello @speich , this functionality has been implemented in v4.4.0 deployed recently. The display callback now receives an optional 2nd parameter event that can be used as necessary display(selectedItem, event?: MouseEvent | KeyboardEvent | null) => {
if (event) {
// do something
}
return `${selectedItem.label}`;
} It defaults to |
Beta Was this translation helpful? Give feedback.
-
As of v4.21.0, there are two ways of doing this as described in the FAQ section of the documents. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be helpful if the
display
method would also have the event passed as an argument (same asonSubmit(event, selectedItem?)
). Then I could discern between click or keyup as well as backspace or other input.Beta Was this translation helpful? Give feedback.
All reactions