[mention] Suggestions won't show up if the editor is focused on componentDidMount
See original GitHub issueIf the editor is focused on componentDidMount
with this.refs.editor.focus();
, the suggestions will never be displayed after typing @
.
The same issue will appear if you have hot reload enable in your setup and if the editor is focused when reloading the component.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:8 (3 by maintainers)
Top Results From Across the Web
How to set focus on an input field after rendering?
@Dhiraj's answer is correct, and for convenience you can use the autoFocus prop to have an input automatically focus when mounted: <input autoFocus...
Read more >4 Ways to Set Focus on an Input Field After Rendering in React
Here is the complete article on how you can set a focus on the input field after rendering in React. Learn autofocus using...
Read more >21 Essential React.js Interview Questions and Answers | Toptal®
Comprehensive, community-driven list of essential React.js interview questions. Whether you're a candidate or interviewer, these interview questions will ...
Read more >How to Search and Filter Components in React - freeCodeCamp
By the end of this tutorial hopefully you will learn how to search through an API and return only the queried results with...
Read more >How to refactor React components to use Hooks
Cover some generic issues with refactoring React components to Hooks that apply to a wide variety of application types.
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 FreeTop 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
Top GitHub Comments
any plans to fix this? i’m really glad i found this bug with a google search, so i could add in the workaround.
@bsapozhnikov glad you figured it out although I’m wondering if we can do something in the core to fix this issue …