Improvements
Triage

Cursor down behavior: make it configurable

What could be better?

In legacy Anytype, if you are somewhere in a text Block and you move the cursor down with the arrow key, the cursor jumps to the end of the Block.

But in AnyTwo, the cursor jumps one Block deeper.

-- Personally, I prefer legacy Anytypes's behavior. But I know, that there are arguments and opinions for/against each one of the two possible variants.
Therefore, I request to let the user make the choice: add a switch in the preferences.

3 Comments

Sign in to comment

R
Ronsox·about 1 hour ago

I personally like the new behavior 🙂

C
Code-Jack·about 1 hour ago

And therefore, I've requested to make it configurable, so that every user can become happy, not matter which behavior he prefers.

AL
Alex Lins (Bao)·about 3 hours ago

Thanks for flagging this — the comparison between legacy and current behavior is clear. To help us prioritize, a couple of quick questions:

  1. How often does this come up for you in practice? Is it a daily friction point, or more of an occasional "I wish it worked this way" thing?
  2. When you say you prefer the legacy behavior (cursor stays in the block), is that because it matches other apps you use, or just feels more natural for your workflow?

This helps us understand whether this needs a preference toggle or if there's a deeper UX pattern we should reconsider.

post_01m48xznt5fev9szxt5dwgr34v