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

Windows: Ctrl + right / left arrows doesn't navigate by word any longer #14170

Closed
afercia opened this issue Feb 28, 2019 · 0 comments · Fixed by #14184
Closed

Windows: Ctrl + right / left arrows doesn't navigate by word any longer #14170

afercia opened this issue Feb 28, 2019 · 0 comments · Fixed by #14184
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Bug An existing feature does not function as intended [Type] Regression Related to a regression in the latest release

Comments

@afercia
Copy link
Contributor

afercia commented Feb 28, 2019

Noticed while re-resting #6002 (comment)

On Windows, standard keyboard shortcuts to move the caret "by word" in a textarea are Ctrl + right arrow and Ctrl + left arrow. This used to work within the blocks rich text area but seems it's now broken.

  • test with any browser on Windows
  • go in a standard textarea, for example in WordPress > Settings > Discussion
  • enter some text in one of the textareas there
  • verify Ctrl + right arrow and Ctrl + left arrow move the caret "by word"

Then go in the Block Editor, create a new post, add same text in a paragraph:

  • Ctrl + right arrow and Ctrl + left arrow move the caret by character
  • expected: by word

Note: Shift + Ctrl + right arrow and Shift + Ctrl + left arrow still work correctly and select text by word

In any editor, standard operations like navigating / selecting text should always work with the native shortcuts. Not to mention the breakage of standard keyboard navigation is even more serious for assistive technologies users.

This appears to have changed at some time, sorry I'm not able to trace down exactly when.

@afercia afercia added [Type] Bug An existing feature does not function as intended [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Regression Related to a regression in the latest release labels Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Bug An existing feature does not function as intended [Type] Regression Related to a regression in the latest release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant