Block-moving keyboard shortcuts fail in a bunch of ways

summary

recent changes to keyboard behavior have regressed our ability to move blocks around with the keyboard and broken the previously clear mental model of block movement.

Previously, there was a clear “slot” before and after every block on the page, and you could reach all of the slots on the page via keyboard. You can no longer move blocks into, out of, or within callouts or columns without experiencing a broken behavior

</aside>

Bug: cannot move content into a callout via keyboard

Steps to Reproduce

select the page content 1 block

move it into the top of the callout block with cmd+shift+↓

🛑 note that step 2 does not work anymore ~ the content moves AFTER the callout

same applies for moving page content 2 into the callout from below with cmd+shift+↑

animated gif of the issue, showing keypresses

Demo Space

page content 1

<position 1>

callout block content 1

callout block content 2

<position 2>

</aside>

page content 2

Bug: cmd+shift+up/down when in text editing mode causes the block to lose focus

Steps to Reproduce

place the cursor in a block

move the block up one space with cmd+shift+up

move it up one space with cmd+shift+up

🛑 BUG: cannot do step 3 because the block has lost focus, so you cannot continually move blocks around unless you stop editing (by pressing ESC between step 1 and 2)

this used to work better, and moving a block would trigger block-editing mode instead of text-editing mode

animated gif of issue, showing keypresses

Demo Space

aaa

bbb

ccc

Bug: cannot move blocks into a column

Steps to Reproduce

create a block before a row of columns

attempt to move the new block into any column with CMD+shift+up/down

🛑 BUG: step 2 is impossible

this is probably the same issue as bug 2, but worth calling out as an acceptance criteria

animated gif of issue, showing keypresses

Demo Space

MOVE ME INTO COLUMN 2 WITH KEYBOARD

column 1

column 2