Using arrow keys to navigate emoji recommendations moves caret #7425

Closed
opened 2025-11-02 07:25:40 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @delvh on GitHub (Jun 3, 2021).

  • Gitea version (or commit ref): 1.15.0+dev-379-gc1ff59c1c
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes

Description

When there is a line above or below the line requesting emojis, the caret will be moved as well when the arrow keys are used to navigate the emoji recommendation. As a result of this, most likely some internal check fails as the caret is not aligned where it is expected to be, and hence no recommendation insertion occurs.

To fix this problem, key input should not be forwarded to the caret while the recommendation popup is present.

Screenshots

image
Shows that the caret has been moved up after clicking . If enter is pressed now, nothing happens except that the menu disappears. Same is true if there is a line below and is pressed.

Originally created by @delvh on GitHub (Jun 3, 2021). - Gitea version (or commit ref): 1.15.0+dev-379-gc1ff59c1c - Can you reproduce the bug at https://try.gitea.io: - Yes ## Description When there is a line above or below the line requesting emojis, the caret will be moved as well when the arrow keys are used to navigate the emoji recommendation. As a result of this, most likely some internal check fails as the caret is not aligned where it is expected to be, and hence no recommendation insertion occurs. To fix this problem, `↑` `↓` key input should not be forwarded to the caret while the recommendation popup is present. ## Screenshots ![image](https://user-images.githubusercontent.com/51889757/120622574-3a100e00-c45f-11eb-9238-3ae59fa05aef.png) Shows that the caret has been moved up after clicking `↑`. If enter is pressed now, nothing happens except that the menu disappears. Same is true if there is a line below and `↓` is pressed.
GiteaMirror added the topic/uiissue/needs-feedback labels 2025-11-02 07:25:40 -06:00
Author
Owner

@wxiaoguang commented on GitHub (Apr 26, 2023):

It has been refactored.

Is there still a problem?

@wxiaoguang commented on GitHub (Apr 26, 2023): It has been refactored. Is there still a problem?
Author
Owner

@wxiaoguang commented on GitHub (May 2, 2023):

I think it has been fixed.

@wxiaoguang commented on GitHub (May 2, 2023): I think it has been fixed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7425