logseq / logseq/db-test

Property values not always displayed after input

Open
#1,038 1 comment 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
  • I searched and no similar issues were found
What Happened?

I have a tag with 3 number properties. Sometimes when I enter a value for the second or third properties and press enter the value disappears. Strangely sometimes entering a different value will work, or just a single digit value.
However if I close and reload Logseq the values reappear.

Reproduce the Bug
  1. create a block with the tag
  2. start entering values for the properties
  3. press enter or right arrow
  4. the value disappears
  5. doesn't always happen, and it is usually only for the second and third properties
Expected Behavior

No response

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

Windows 11
Logseq 2.0.1-alpha+nightly.20260728
Also the beta version 2.0.1

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

No files or tests are identified. Start by reproducing the issue on Windows 11 with Logseq 2.0.1-alpha or beta, following the numbered steps and testing the second and third number properties; done means entered values remain visible after pressing Enter or the right arrow without needing to reload.

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
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.