Skip to content
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

Gutenberg: Keyboard Shortcut Results in Backspace #28834

Closed
Aurorum opened this issue Nov 25, 2018 · 3 comments
Closed

Gutenberg: Keyboard Shortcut Results in Backspace #28834

Aurorum opened this issue Nov 25, 2018 · 3 comments
Assignees
Labels
[Goal] Gutenberg Working towards full integration with Gutenberg OSS Citizen [Pri] Low [Type] Bug

Comments

@Aurorum
Copy link
Contributor

Aurorum commented Nov 25, 2018

Steps to reproduce

  1. Starting at URL: https://horizon.wordpress.com/gutenberg/post/
  2. Start a paragraph block
  3. Write a word in it
  4. Make it italics/bold
  5. Hit your spacebar
  6. Use your keyboard shortcut to turn off italics (cmd + I on my device)
  7. Type another character
  8. See issue

What happened

Instead of starting a new word without formatting, the text you type will just be added to your previous word, and remain in bold/italics.

What I expected

On previous editors, a new word will be started which has no formatting. This should happen with Gutenberg too.

Browser / OS version

Mac OS X 10.6.8
Chrome 49.0.2623.112

Context / Source

I found this whilst writing a post myself for the first time with Gutenberg. I'm used to being able to disable formatting for the next word with a keyboard shortcut, and I'm sure many others too. This bug ruins that flow with Gutenberg.

@gwwar gwwar added [Goal] Gutenberg Working towards full integration with Gutenberg [Type] Bug labels Nov 25, 2018
@vindl
Copy link
Member

vindl commented Dec 10, 2018

Thanks for the report @torres126! This issue seems to be occurring in core Gutenberg too. Could you please report it there and link back here with the created issue?

We usually try to keep integration related issues in Calypso repository, and to escalate anything that also affects the core project in the Gutenberg repository. One easy way to rule out a core bug that I often use is testing with Gutenberg demo on https://wordpress.org/gutenberg/.

@Aurorum
Copy link
Contributor Author

Aurorum commented Dec 10, 2018

Thanks for that tip! It looks like this has been mentioned over there already, but I'll bare that tip in mind in the future. :)

@vindl vindl self-assigned this Dec 11, 2018
@vindl
Copy link
Member

vindl commented Dec 11, 2018

Awesome, thanks for locating it! I forgot to mention an important step there - before reporting we should check if the issue already exist. :)

Closing since there is already a filed core issue for this: WordPress/gutenberg#12529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Goal] Gutenberg Working towards full integration with Gutenberg OSS Citizen [Pri] Low [Type] Bug
Projects
None yet
Development

No branches or pull requests

4 participants