logseq / logseq/db-test

Incorrect child block UI when a hidden property has an empty value

Open
#1,189 2 comments 0 reactions 1 assignee View on GitHub

@tiensonqin is already working on this.

Since Sep 17, 2026.

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

Description

Search first
  • I searched and no similar issues were found
What Happened?

The child block UI is displayed incorrectly when a block contains a hidden property with an empty value.

Even though the block has no child blocks other than the empty property, the UI incorrectly displays the expand/collapse control as if the block had children.

Reproduce the Bug
  1. Create a block with a property that has an empty value.
  2. Hide the property from the UI.
  3. Make sure the block has no child blocks other than the hidden empty property.
  4. Observe the block's child block UI.
Expected Behavior

The expand/collapse control should not be displayed because the block has no child blocks.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

windows 11
logseq 2.0.1-alpha+nightly.20260907

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.