MySQL Bugs: #94430: Up and down keyboard keys not behaving normally on the SQL editor

Bug #94430	Up and down keyboard keys not behaving normally on the SQL editor
Submitted:	21 Feb 2019 21:25	Modified:	24 Jun 2019 20:58
Reporter:	Romain Riche	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	8.0.15	OS:	MacOS
Assigned to:		CPU Architecture:	x86
Tags:	down, editor, keyboard, SQL, up

Description:
up key doesn't (always) go up
down key doesn't (always) go down

How to repeat:
For example: SQL editor loaded with say 100 lines and the actual window size only showing 30 lines. then: Pressing up or down keyboard keys makes the cursor move correctly until it reaches the first or 30th lines then revert the way, if going up it will then go down and reverse... 

=> the up and down keyboard keys have no impact on the editor scrollbars.

very frustrating bug that prevents the use of the the up and down keys.

Suggested fix:
fix the behaviour of navigating the editor with keyboard key press up and down

This problem is already known and requires an upgrade of the used 3rd party editor component (which is planned already).

The workaround is pretty simple, however: when you open an SQL editor once scroll the content vertically using the mouse wheel/trackpad. After that the arrow keys behave (mostly) as they should.

Sorry for the inconvenience.

Thank you for the bug report.

It's not just the view port that doesn't scroll properly, but pressing up and down will often times jump to the next query instead of the next line, and sometimes it scrolls in reverse (pressing down arrow sends the cursor to the line above).

still not fixed in 8.0.16
any chance to have it on 8.0.17 ?

Bug #95385 marked as duplication of this one.

Fixed as of the upcoming MySQL Workbench 8.0.18 release, and here's the changelog entry:

On computers running MacOS, the up and down arrow keys, at times, reversed
direction or moved to the next (or previous) query, instead of to the next
(or previous) line.

Thank you for the bug report.