-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Space after italics gets deleted when using keyboard shortcut #12529
Comments
I was having the same issue yesterday and came here today to report it. On testing again today, though, I was not able to reproduce the issue in either the latest versions of Firefox or Chrome. I'm running WordPress 5.0.2 and the Gutenberg plugin is deactivated. @killermann - I'm curious if you can reproduce the issue again? |
I can confirm that this can still be reproduced with Gutenberg on WordPress.com. |
@sirjonathan just give it a go in Chrome with WP 5.0.2 (not Gutenberg plugin). Identical behavior to my screen recordings above. So, on my end, still a bug. One change: I'm not seeing all the spam in the output, so that's progress. (sorry for the delay -- holidays and whatnot) |
Hi folks! I was able to reproduce this using a Jurassic Ninja site and it also happens when you use the "Bold" button. Here's what I got: Since the space is deleted, the text will go back to bold. I wasn't able to reproduce this in the Classic Editor. WordPress 5.0.3 running Twenty Nineteen theme. Chrome Version 71.0.3578.98 (Official Build) (64-bit). macOS Mojave 10.14.2 |
Describe the Bug
When writing, if you use keyboard shortcut for italics (or bold), then hit space before un-italicizing, the space gets deleted when you un-italicize, and any further typing gets italicized and combined to the previous word.
Steps to reproduce the behavior:
Expected behavior
Ideally, the editor would put a closing tag on the last character before the space, and allow you to keep typing un-italicized (or un-bolded, etc.).
At the very least, there should be a non-breaking space after the character, then the closing tag.
In either case, you would be able to continue writing un-interrupted. Right now, it requires you to use the mouse to fix, or the right arrow key, which is disruptive to the user's writing flow.
Screenshots
Here's a gif of a short video of the behavior: https://imgur.com/iYvzfBG
I hope it helps, because this was a weird one to describe.
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: