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

Feedback on return keyboard behavior for List V2 #40767

Closed
annezazu opened this issue May 2, 2022 · 1 comment
Closed

Feedback on return keyboard behavior for List V2 #40767

annezazu opened this issue May 2, 2022 · 1 comment
Labels
[Block] List Affects the List Block [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable

Comments

@annezazu
Copy link
Contributor

annezazu commented May 2, 2022

What problem does this address?

As part of the fourteenth call for testing for the FSE Outreach Program, it was noted in a group call for testing that entering twice would be expected to outdent rather than indent.

What is your proposed solution?

Consider having entering twice match what one experiences in other word processors (like google docs). In both videos below, I'm hitting the return keyboard key.

Block Editor:

indent.twice.mov

Google doc:

google.doc.mov
@annezazu annezazu added [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable [Block] List Affects the List Block [a11y] Keyboard & Focus labels May 2, 2022
@ntsekouras
Copy link
Contributor

Resolved by this one: #40939. Small naming mix up 😄

@priethor priethor added the [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] List Affects the List Block [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable
Projects
None yet
Development

No branches or pull requests

3 participants