Opened 7 years ago
Closed 4 months ago
#45527 closed defect (bug) (invalid)
Jumping Cursor in Gutenberg Editor
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 5.0 |
| Component: | Editor | Keywords: | close |
| Focuses: | ui, administration | Cc: |
Description
While typing in a block / paragraph, the cursor jumps to the beginning of the paragraph. It happens while autosaving or language-correction. I testet Firefox 63, Edge and Chromium (all Windows 10). All WordPress-plugins were disabled, alls browser-plugins disabled. No mouse-movement at this moment, no keybord-buttons pressed.
This problem happens since the 5.0 update.
Video of the problem: https://youtu.be/yJ2qSLq9hMs
In the video: I type some text and wait. While waiting the cursor jumps to the start of the paragraph. If I go on writing, the text is written at the beginning.
Change History (8)
This ticket was mentioned in Slack in #core-editor by jeremyfelt. View the logs.
7 years ago
#4
in reply to:
↑ description
@
7 years ago
We are experiencing the same problem. It began after updating to WP 5.0. And autosave occurs every 15 seconds so it has become impossible to use.
Replying to pascalts:
While typing in a block / paragraph, the cursor jumps to the beginning of the paragraph. It happens while autosaving or language-correction. I testet Firefox 63, Edge and Chromium (all Windows 10). All WordPress-plugins were disabled, alls browser-plugins disabled. No mouse-movement at this moment, no keybord-buttons pressed.
This problem happens since the 5.0 update.
Video of the problem: https://youtu.be/yJ2qSLq9hMs
In the video: I type some text and wait. While waiting the cursor jumps to the start of the paragraph. If I go on writing, the text is written at the beginning.
#5
@
7 years ago
I experience this bug, but only with my Genesis theme (Mai Pro) active. When I switch to 2019, this bug goes away. I think this is a theme bug, not a core bug.
#6
@
7 years ago
We traced the bug in Mai Theme back to an issue in CMB2 that has already been patched (in CMB2). It may be worth activating CMB2 (2.6) from the WP repo to see if the issue goes away. There are lots of factors in this issue, but many may be related to CMB2 since many themes/plugins use the library.
#8
@
4 months ago
- Keywords close added; needs-patch needs-testing removed
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
Unless I am mistaken, this means that the issue has been narrowed down to being a bug within the theme. I am unable to replicate outside of that. For now, I am going to suggest we close this and then we can always consider our approach if more details surface, for example reporting through the core editor Github would be my recommendation: https://github.com/WordPress/gutenberg/issues/new/choose
I also had this issue using Version 70.0.3538.110 (Official Build) (64-bit) of Chrome on Mac OS.