Stuck on an issue?
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.
Select.Async do not handle IME after update to v1.0.0-beta14
See original GitHub issueFirst, thank you for the awesome component 😃 It’s really helpful!
After update to v1.0.0-beta14 from v1.0.0-beta13,
Select.Async do not handle IME well. (Select works well)
After every loadOptions call, the input is fixed and IME do not work.
I prepare a plnkr to show it, https://plnkr.co/edit/IjHgD1RboVuspyhUQbJM?p=preview
Could you help me ? Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:9
Top Results From Across the Web
React Select Async creatable doesn't save to the state
I am using react select async creatable, the data from api loads correctly and can select it also can create new values but...
Read more >react-select-migrate - npm
React-Select v2 is a complete rewrite, all new with some major API ... you must handle the change and pass the updated value...
Read more >ChangeLog.md · an-tao/drogon - Gitee.com
Check HTTP client is not sending requests in sync mode on the same event loop. Start listening after beginning advices.
Read more >API - React Select
If provided, this will be called with the input value when a new option is created, and onChange will not be called. Use...
Read more >react-select | Yarn - Package Manager
It represents a whole new approach to developing powerful React.js components that ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@apearce It works with
ignoreAccents={false}and not work withignoreAccents={true}. You are right, it should be work both way. I reopen this issue.Setting
ignoreAccentsto false solves this issue. It should probably be false by default anyway. What is odd is this prop was in well prior to beta13 but from what I can tell the issue didn’t arise until this commit which came well after beta13 was released.