Clicking on an editor doesn't always give focus
See original GitHub issueDo you want to request a feature or report a bug?
I’m reporting a bug: when using multiple editors on the same page, moving the focus from one editor to the next with the pointer is unreliable.
What’s the current behavior?
With more than one editor on the same page, clicking from one editor to another does not always give it the focus. The behavior is non-deterministic (as a far as I can tell), and it sometimes works.
This can be reproduced on the Syncing Operations
example on the SlateJS website.
(For this reason, I’m not including a Fiddle).
My setup:
- MacOS
10.14
- Chrome
68.0.3440.106
- Slate
0.40.2
What’s the expected behavior?
The focus should reliably move to an editor when clicking on it.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Problem with losing focus on all editors. Forum editor, Word ...
The page or editor will lose focus and you have to click on the editor agian to regain the focus and typing position....
Read more >HTML input fields does not get focus when clicked
when i click it the field does not get the focus. i can access the field via pressing the "tab-key". It sounds like...
Read more >The editor window doesn't want to let go of focus
If I am in the editor window, then click another window (i.e. Safari, Mail, etc.), that window will gain focus for a half...
Read more >Inconsistent behavior among browsers when clicking on buttons
When you click on a button in Safari (12.1.1), the button does not get focus. The document gets focus instead. We know this...
Read more >"Link with editor" does not work when "Focus on active task" is ...
Moreover, you cannot switch "Link with Editor" on, without previously switch "Focus on active task" off... or, at least, the UI gives you...
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
I still seeing this issue on slate: “0.44.9” slate-react: '0.21.15"
I can confirm this. Having two editor components with just the “getting started” editor renders one editor unusable.
I also tested earlier versions and this already seems to be buggy with
“slate”: “0.37.4”, “slate-react”: “0.15.5”,