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

Add keyboard shortcuts for moving blocks #10455

Closed
ZebulanStanphill opened this issue Oct 9, 2018 · 11 comments · Fixed by #23276
Closed

Add keyboard shortcuts for moving blocks #10455

ZebulanStanphill opened this issue Oct 9, 2018 · 11 comments · Fixed by #23276
Assignees
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). Needs Dev Ready for, and needs developer efforts [Status] In Progress Tracking issues with work in progress [Type] Enhancement A suggestion for improvement.

Comments

@ZebulanStanphill
Copy link
Member

ZebulanStanphill commented Oct 9, 2018

The issue

Currently, there is no way to move a block when the side controls are not shown. Ideally, there should be keyboard shortcuts for moving blocks up and down.

Proposed solution

In #71 I noticed that the following was suggested as the macOS shortcut:

Move block up: ^Ctrl+⌥Option+
Move block down: ^Ctrl+⌥Option+

If these were used, the Windows and Linux equivalents would be:

Move block up: ⇧Shift+⎇Alt+
Move block down: ⇧Shift+⎇Alt+

@mtias
Copy link
Member

mtias commented Oct 9, 2018

Ulysses uses ⌃⌘↑ and ⌃⌘↓ for this functionality.

@ZebulanStanphill
Copy link
Member Author

@mtias What would the Linux/Windows equivalent of those be?

@designsimply designsimply added [Type] Enhancement A suggestion for improvement. [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). labels Oct 16, 2018
@afercia
Copy link
Contributor

afercia commented Feb 24, 2019

Related #11154 and #3218.

@ervind
Copy link

ervind commented Mar 27, 2020

Are there any moves forward with this one?

It would really mean improvements in usability. Imagine a 2000 word-long article where you have to duplicate some paragraphs and move them to the bottom.

Now I have 2 options:

  1. drag&drop
  2. clicking on the down arrow a million times

It would be a lot more comfortable if I could move it up/down with pressing some keys on my keyboard (e.g. simulating the clicks on the arrows).

@daveredfern
Copy link

+1 Amazed this isn’t implemented yet.

@jakyo-dev
Copy link

jakyo-dev commented Apr 7, 2020

I frequently stumble upon this issue as well. The main issue is when the arrow icons change their position on the display slightly, leading to a lot of missclicks.

I tested some expected shortcuts (Windows: arrow keys with either cmd, alt or shift) and was surprised it's not implemented. The following google search led me here.

@zieliz
Copy link

zieliz commented May 9, 2020

I would love this! I don't want to keep clicking.

@mtias mtias added the Needs Dev Ready for, and needs developer efforts label May 11, 2020
@jeremyfelt
Copy link
Member

jeremyfelt commented May 28, 2020

Ulysses uses ⌃⌘↑ and ⌃⌘↓ for this functionality.

Dropbox Paper also uses ⌃⌘↑ and ⌃⌘↓.

Big 👍🏻

@ellatrix
Copy link
Member

Now I have 2 options:

  1. drag&drop
  2. clicking on the down arrow a million times

There's also copy paste.

@ZebulanStanphill
Copy link
Member Author

It's worth noting that, on a keyboard, after you've focused one of the movers, you can just press Space to press it. (This works for all HTML <button>s, actually.)

@mtias
Copy link
Member

mtias commented Jun 4, 2020

There's also copy paste.

And this one is in progress: #22031

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). Needs Dev Ready for, and needs developer efforts [Status] In Progress Tracking issues with work in progress [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.