Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

默认富文本编辑器中紧跟表格后的文本选中后无法删除 #5193

Closed
LIlGG opened this issue Jan 16, 2024 · 0 comments · Fixed by #5234
Closed

默认富文本编辑器中紧跟表格后的文本选中后无法删除 #5193

LIlGG opened this issue Jan 16, 2024 · 0 comments · Fixed by #5234
Labels
area/console Issues or PRs related to the Halo Console area/editor Issues or PRs related to the Editor kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@LIlGG
Copy link
Member

LIlGG commented Jan 16, 2024

系统信息

使用的哪种方式运行?

Docker

在线站点地址

No response

发生了什么?

默认富文本编辑器中,当表格下存在文本时,选中文本无法对文本进行删除。

正常的操作应该是选中文本也可以进行删除。

/area console
/area editor
/kind bug

相关日志输出

No response

附加信息

No response

@f2c-ci-robot f2c-ci-robot bot added area/console Issues or PRs related to the Halo Console area/editor Issues or PRs related to the Editor kind/bug Categorizes issue or PR as related to a bug. labels Jan 16, 2024
@LIlGG LIlGG added this to the 2.12.x milestone Jan 23, 2024
f2c-ci-robot bot pushed a commit that referenced this issue Jan 24, 2024
#### What type of PR is this?

/kind bug

#### What this PR does / why we need it:

当表格后存在选中的内容时,按下退格键或删除键不再执行选中表格的操作,而是继续向下执行。

#### How to test it?

在表格后紧跟着文本,从文本开头选中文本,然后按下退格键,查看文本是否能够被删除。

#### Which issue(s) this PR fixes:

Fixes #5193 

#### Does this PR introduce a user-facing change?
```release-note
解决默认富文本编辑器中表格后的文本选中后无法删除的问题
```
@ruibaby ruibaby modified the milestones: 2.12.x, 2.12.0 Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/console Issues or PRs related to the Halo Console area/editor Issues or PRs related to the Editor kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants