You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Navigate to the autosuggest input using keyboard (Tab). Do not click the input.
Press the arrow down key.
What happened:
Receive the error: TypeError: Cannot read property '0' of undefined.
Problem description:
computed_section_default0 is not being populated unless the input receives a character or is clicked.
Suggested solution:
As a workaround to this issue, I provided an override to the handleKeyStroke method in the mounted hook of my component:
patchAutoSuggestKeystrokeBug() {
const autoSuggest = this.$refs.autosuggest;
const originalHandleKeyStrokeFunc = autoSuggest.handleKeyStroke;
this.$refs.autosuggest.handleKeyStroke = function (e) {
// Simulate a click on ArrowDown to open the list of suggestions
if (e.keyCode === 40 && autoSuggest.$data.currentIndex === null) {
autoSuggest.listeners.click();
autoSuggest.$data.currentIndex = 0;
return;
}
originalHandleKeyStrokeFunc(e);
};
},
This allows the list of suggestions to open when the arrow key down is pressed in this scenario, rather than erroring.
The text was updated successfully, but these errors were encountered:
vue-autosuggest
version: 2.2.0node
version: 14.18.1npm
(oryarn
) version: yarn 1.22.15Relevant code or config
Standard implementation.
What you did:
Navigate to the autosuggest input using keyboard (Tab). Do not click the input.
Press the arrow down key.
What happened:
Receive the error: TypeError: Cannot read property '0' of undefined.
Problem description:
computed_section_default0
is not being populated unless the input receives a character or is clicked.Suggested solution:
As a workaround to this issue, I provided an override to the handleKeyStroke method in the mounted hook of my component:
This allows the list of suggestions to open when the arrow key down is pressed in this scenario, rather than erroring.
The text was updated successfully, but these errors were encountered: