search

logseq / logseq

A privacy-first, open-source platform for knowledge management and collaboration. Download link: http://github.com/logseq/logseq/releases. roadmap: http://trello.com/b/8txSM12G/roadmap
https://logseq.com
GNU Affero General Public License v3.0
32.14k stars 1.87k forks source link

[Drag-and-drop] Moving non-selected blocks, while some other are selected doesn't work #9782

Open stdword opened 1 year ago

stdword commented 1 year ago

Search first

What Happened?

Cant't drag & drop non-selected blocks if there are selected ones.

Demo:

Note: Blocks are moving, but selected ones, not dragging ones. In the Demo I've trying to move text 1 and text 4, but moves text 3.

Note: In the end of the demo all blocks suddenly have been selected.

Reproduce the Bug

  1. Select any block (press ESC in edit mode)
  2. Try to drag'n drop ANOTHER block
  3. Result: The selected one was moved.

Expected Behavior

The dragged one should be moved instead.

Desktop or Mobile Platform Information

MacOS v13.4 Logseq Desktop v0.9.10

stdword commented 11 months ago

Hello! Guys, did you miss that issue? I guess this is an important ux one

@Bad3r could you assign a label or summon someone from the team?) 🙏

github-actions[bot] commented 5 months ago

Hi There! 👋

We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉 We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!

N1N74 commented 5 months ago

Not OP but it still happens in Logseq v0.10.7 windows. Extremely annoying and outstanding bug imho.

stdword commented 5 months ago

And still actual in v0.10.8