Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dropdown: Controlled Dropdown component ignores spaces
See original GitHub issueBug Report
Steps
Create a controlled Dropdown component and by controlled I mean setting the open prop manually.
Then, add a debounced onSearchChange callback. The problem here apparently stems from the fact that I am setting open prop in a debounced function. After first call of this function I am able to properly type words separated by a space.
Expected Result
Changing the search query would properly register each character.
Actual Result
Apparently typing e.g. adam tr ignores the space in between the words.
Version
0.82.4
Testcase
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Why does it even behave like this? Why should the dropdown show the options after typing a space? I can’t come up with a good usecase for a situation where I would like the dropdown to be open on pressing space.
A fix was released in
semantic-ui-react@1.2.1🎉