CMD+X jumps cursor up one block after cutting text

What’s The Bug?

CMD+X jumps cursor up one block after cutting text in macOS

How To Reproduce It

Create a page with two blocks of text. Select text in the lower block and press cmd+x. This causes the cursor to jump up one block

Image or Video

The Expected Behavior

The cursor should remain where it was when I selected the text to cut.

Device

MacBook Pro M1 Max 2021

OS

Sequoia 15.4.1

Anytype Version

v0.46.1

Network Mode

AnySync

Technical Information

OS version: darwin arm64 15.4.1
App version: 0.46.1
Build number: build on 2025-04-17 20:22:50 +0000 UTC at #de38863027eb064b5b0ec258ce088fc45cb213cb
Library version: v0.40.16
Anytype Identity: A7x9qifMvXzYb3xNjzSQZUtNakuAYEw1xaXhtR1uzJsjgQPu
Analytics ID: 4c4c4c3d-3bdb-47dc-b409-b75bcec4afec
Device ID: 12D3KooWEuWGqUcbs78q5wYFG3hU5aBE87mABADge4kXLQmMEsWY
Ethereum Address: 0x626b4C7988493D966cCb19E555891982488f96CA

What’s The Bug?

on CUT command, cursor jumps to the end of previous paragraph instead of staying in place

How To Reproduce It

1.have at least 2 paragraphs of text
2.select a word in the second paragraph
3.cut-command the word (CMD+X)
4.the cursor jumps to the end of previous paragraph.

Image or Video

The Expected Behavior

cursor should stay in place

Device

MacBook Pro 2023

OS

15.3.1

Anytype Version

0.45.2

Network Mode

Anysync

Technical Information

OS version: darwin arm64 15.3.1
App version: 0.45.2
Build number: build on 2025-02-13 11:57:09 +0000 UTC at #2c0826b346001f15fd0f9c720a83db8487e269a1 (dirty)
Library version: v0.39.10
Anytype Identity: A7yjE9EtxnVYHuGDP8EPoQ7HpoVkc3tt4gJijkE87kgN2yha
Analytics ID: 7d843c40-0aec-4d37-888b-f707680798ef
Device ID: 12D3KooWEsyefCKzPnh2fSmeqqSk5NUNSzkcC5egMYyrwsKU72WH

I’m new to Anytype, facing the exact same issue with 0.45.3 on x64 Macbook Pro 2015 with macOS 12.7.6.

I can confirm this on MacOS 15.3.2 and Anytype 0.45.12-beta.

I can confirm the issue on a Framework 13 AMD running Fedora Linux 42 (KDE Desktop).
Interestingly I didn’t have this issue until now.

Using AnyType 0.47.3

Duplicate: