Keyboard Navigation Issue

WHAT IS THE BUG

Using the up and down arrow keys to navigate between blocks achieves a likely unintended result and inconsistencies that should be fixed or planned out. I will attempt to explain below.

HOW TO REPRODUCE IT

Part 1: Navigating Down
Navigating down on a multi line block

  1. Create a multiline block with text.
  2. Navigate down starting with the empty block above the multiline block you just created.
    RESULT: The input curser position goes to the beginning line of every multiline set of text. When no other multiline is available, the input curser moves from the beginning of the last line to the very end of the last line. (Video below)

Navigating down on a single line block

  1. Create multiple single line text blocks.
  2. Navigate down through the single line blocks starting with an empty block above.
    RESULT: The input curser position goes to the beginning and end of every single line block. (Video below)

Part 2: Navigating Up
Navigating up on a multi line block

  1. Create a multiline text block
  2. Navigate up starting with an empty block below the multiline block.
    RESULT: The input curser position goes from the empty block to the end line of the multiline block. It then continues navigating to the end of every multiline block until the last line is reached. It then moves to the beginning of the line. (Video below)

Navigating up on a single line block

  1. Create multiple single line text blocks.
  2. Navigate up starting at the empty single line block below.
    RESULT: The input curser position goes from the empty block below and cycles through every line end to line beginning (Video below)

THE EXPECTED BEHAVIOR

This can be confusing to a user and they would expect the cursor to move in the manner they expect. For example: Moving down would move the cursor to the next block down. If it is a multi line text block, the user would expect the cursor to move directly below to the next line or the next block if it is the last line.

SYSTEM INFORMATION

OS version: win32 x64 10.0.19045
App version: 0.31.72-beta
Build number: build on 2023-06-13 20:48:15 +0000 UTC from at #0fa0c6245a6b523e1830aa38e9184a0a7ec42fad(v0.27.2)
Library version: v0.27.2
Analytics ID: AAb3CnvsiL23WvBh5o1b6BBgzuudiVtAbWNHuBaddtcUwQsX
Device ID: A8cTVfDHfqd92UWdRi7p2jKvHYouXHR8p9XtXEoeEBFC9icE

ADDITIONAL CONTEXT

Unsure if this is actually intended or not. My thoughts are it creates a level of inconsistency from what people expect. Additionally, this creates a learning curve that could be hard to break due to the “against the grain” nature of what people expect.

There was a bug report that may be related due to it being used in a feature update. The opposite keys but still having to do with navigation and being used to update code. I will say that is working as intended. Linking below.