logseq / logseq/db-test

Property UI position is not changed correctly

Open
#1,221 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

The UI position of a property is not changed correctly.

### Reproduce the Bug

1. Create a property whose UI position can be changed and apply it to a block.
2. Change its UI position several times.

### Expected Behavior

The UI position should be changed, and the change should be reflected immediately.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

windows11
logseq 2.0.1-alpha+nightly.20260916

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Logseq on Windows 11 using the reported nightly version: create a property, apply it to a block, and change its UI position several times. Trace the property UI position update path; done means each change is reflected immediately and consistently.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.