When editing a header the # isn't shown anymore (unable to remove format with keyboard)
Nobody has claimed this yet.
- #13381 by @tiensonqin — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- frontend
Research direction
Reproduce the issue in version 2.0.1 on test.logseq.com using the listed steps, focusing on heading blocks while editing and deleting their text. The fix is done when the # heading format is visible during editing and an empty block no longer retains heading formatting.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
When you try to edit a heading it won't show the heading format (#) anymore. See attached screenshot. Also the format of the header stays in the block when the text is removed, see second screenshot.
First capture:
Second capture (formatting stays in place while there is not header text).
Reproduce the Bug
- Write something #Test
- Go to a new line, go back to the previous block. Notice that there isn't any # shown.
- Now remove the text 'Test'
- Go to a new line. Notice that the format of the header # is still shown although there isn't any text.
Expected Behavior
Show header format with the #.
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
2.0.1 Windows and test.logseq.com
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!)
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logseq/db-test
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Table filter "does not contain" is case-sensitive while "contains" is notPossibly taken @tiensonqin claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Sorting a tag table by a checkbox gives the same order ascending and descendingPossibly taken @tiensonqin claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Potential Dataloss: Deleting an entry from the property page's node table has no confirmation dialogPossibly taken @tiensonqin claimed this 15 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Similar issues
-
beta technical-medium ui
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
walletbeat/walletbeat#1625 ·
Maintainers usually reply within 1 day
-
[Bug] The clients language filter cannot select the rows the page labels as unknownPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/rocketmq-dashboard#6103 ·
Maintainers usually reply within 4 days
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#18652 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
cockpit-project/cockpit-machines#2835 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/kumo#866 ·
Maintainers usually reply within 1 day