logseq / logseq/db-test

Properties are shown in page properites, even when they're set to beginning/end of the block

Open
#997 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?

After the updates in last few weeks, my properties that are set to beginning or end of the block are also shown in page properties. Tags attached to a block as expected but for pages, their properties are shown below as well regardless of the selected UI position.

### Reproduce the Bug

1. Create a new property.
2. Set it's UI position to beginning or end of the block.
3. Add the property to #journal, a page or some other tag.
4. See the issue.

### Expected Behavior

Before the last few weeks update, the app used to respect the select UI position & not always shown below page title.
Here is what I see in my desktop app(2.0.1-alpha+nightly.20260623) that I haven't updated to latest nightly(& test.logseq.com) which has this issue.
Image

### Screenshots

Issue:
Image

### Browser, Desktop or Mobile Platform Information

Logseq: test.logseq.com, v 2.0.1 [12fc66e](https://github.com/logseq/logseq/commit/12fc66e)

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 test.logseq.com using Logseq v2.0.1 at commit 12fc66e, following the listed steps for a property positioned at the beginning or end of a block. Compare the behavior with the older desktop version shown in the report; done means page properties respect the selected UI position instead of always appearing below the page title.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.