logseq / logseq/db-test-cn

新块中按 Backspace 会退出块编辑状态

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Description

### Search first

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

### What Happened?

在 test.logseq.com 中,如果在一个新块中按 `Backspace` 的话,test.logseq.com 会直接退出块编辑状态,如果我需要编辑这个块的话,我需要用鼠标重新去点一下,不方便

如果在 `0.10.10-alpha+nightly.20240805` 版本中的新块按 `Backspqce` 不会退出编辑状态

不知道这是不是 bug,但对于习惯用快捷键的用户来说,编辑体验很不好,不喜欢写到一半去用鼠标

### Reproduce the Bug

## 在 test.logseq.com 中复现:

![db 版](https://github.com/user-attachments/assets/d61163a0-4cf1-491b-b59c-3c83c64c9548)

1. 在一个新块按 `Backspace`,logseq 就会直接退出编辑状态
2. 我需要用鼠标重新去点一下才能进入编辑状态

## 在 `0.10.10-alpha+nightly.20240805` 版本中复现:

![md 版](https://github.com/user-attachments/assets/9c755610-9c40-496c-9c5b-da1e17ef0e72)

1. 在一个新块按 `Backspace`,logseq 不会退出编辑状态

### Expected Behavior

在新块中按 `Backspace` 键的逻辑修改回 `0.10.10-alpha+nightly.20240805` 的逻辑

### Screenshots

_No response_

### Browser, Desktop or Mobile Platform Information

Windows23H2 Edge浏览器 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!)

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 on Windows 23H2 with Edge by pressing Backspace in a new block, then compare the behavior with version 0.10.10-alpha+nightly.20240805. Done means Backspace no longer exits block editing in a new block and the behavior matches the referenced version.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.