Editor navigation: Allow jumping page up/down with the corresponding keyboard keys

WHAT DO YOU RECOMMEND?

A PC keyboard has the keys “Page up” and “Page down” for jumping one screen page higer/lower each time one of these keys is pressed.
But that doesn’t work in Anytype. There is also not such an entry in the list of keyboard shortcuts.

HOW COULD IT BE DONE?

Support the keyboard keys “Page up” and “Page down”.

REAL WORLD USE CASES

A faster and more comfortable way for reading / scrolling through long Pages.

RECOMMENDED ALTERNATIVES

The user @Uvann asked for scroll up/down buttons on the screen in his FR:

I personally think that these buttons are not necessary, because the TOC is much more comfortable then manual scrolling. Also I think that support for the keys I’ve mentioned would be the better choice, because one simply expects that these keys work.

ADDITIONAL CONTEXT

Btw.: I would have sworn that these keys once have worked. I was astonished when I found out, as I wrote my answer in the linked thread, that these keys don’t work as expected “anymore”.

Which app version are you using? They seem to work just fine for me in 0.52.4.

@Filip since today v0.52.4 but when I wrote the request it was v0.52.3
It doesn’t work in any of these versions.

When I press the page down key, the position jumps a screen page deeper for a split of a second, but it jumps back immediately.

The same applies to the macOS shortcut: fn + arrow-up and fn + arrow-down doesn’t work for objects in modal view. v 0.52.7-alpha here, which is not very different from 0.52.4.

The keys do work, as well as Home / End. However, if you have a cursor in the text somewhere, it will scroll once and then come back. Remove the focus by clicking between the Title and the Publish (globe) button, for example.Then the keys work again. :slight_smile:

If you remove the focus by clicking on the ToC sidebar, then the keys don’t work.

I know this is probably not planned that way but consider it a workaround.

Hey man, you’re good!
Thanks!

This issue has been fixed by the Development Team and will be implemented in an upcoming release.