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.

Sign up for GitHub

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

Jump to bottom

Wrong Handling of Enter Key when using an IME (Web Version Only) #135

Closed
krille-chan opened this issue Jul 15, 2023 · 2 comments
Closed

Wrong Handling of Enter Key when using an IME (Web Version Only) #135

krille-chan opened this issue Jul 15, 2023 · 2 comments
Labels
Needs upstream fix The issue cannot be fixed in this project and waits for an upstream fix. stale The item is going to be closed soon because of inactivity

Comments

@krille-chan
Copy link
Owner

Description

When I am using the Fluffychat Web together with an IME (for example Microsoft Pinyin), an enter key will cause the currrent draft of message to be sent, and then the IME content showing up in the input box.

To Reproduce

Enable IME, type something and trying to use enter to put the raw input on the IME candidate box.

Additional information:

  • Device: Web
  • OS and OS version: Windows 11. Brave browser, latest stable.
  • Installed version of FluffyChat: fluffychat.im/web
@basings basings mentioned this issue Jan 23, 2024
Closed
@Henry-Hiles Henry-Hiles mentioned this issue Feb 7, 2024
Closed
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 6, 2024

This issue is stale because it has been open for 120 days with no activity.

@github-actions github-actions bot added the stale The item is going to be closed soon because of inactivity label Mar 6, 2024
@github-actions GitHub Actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 21, 2024
@farchord farchord mentioned this issue Apr 4, 2024
Open
@angloromanticism angloromanticism mentioned this issue Apr 23, 2024
Open
@Mek101 Mek101 mentioned this issue May 2, 2024
Open
@jfhc jfhc mentioned this issue May 9, 2024
Open
@JacketedSquash6 JacketedSquash6 mentioned this issue May 13, 2024
Open
@HarHarLinks HarHarLinks mentioned this issue May 19, 2024
Open
@dttocs dttocs mentioned this issue Jun 14, 2024
Closed
@marek-lach marek-lach mentioned this issue Jun 22, 2024
Closed
@andrewgdotcom andrewgdotcom mentioned this issue Jun 27, 2024
Open
@gentleAmateur gentleAmateur mentioned this issue Jul 7, 2024
Open
@dav23r dav23r mentioned this issue Jul 10, 2024
Open
@wanderson24 wanderson24 mentioned this issue Jul 15, 2024
Open
@rhinux rhinux mentioned this issue Jul 29, 2024
Open
@hesshu hesshu mentioned this issue Jul 31, 2024
Open
@Saskia137 Saskia137 mentioned this issue Aug 6, 2024
Open
@isilzha314 isilzha314 mentioned this issue Aug 12, 2024
Open
@phtnnz phtnnz mentioned this issue Aug 13, 2024
Open
@WilsonFung418 WilsonFung418 mentioned this issue Aug 17, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs upstream fix The issue cannot be fixed in this project and waits for an upstream fix. stale The item is going to be closed soon because of inactivity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@krille-chan