# \[Web Beta\] Issue with Korean input and spacebar registration on Windows

**URL:** <https://community.bear.app/t/web-beta-issue-with-korean-input-and-spacebar-registration-on-windows/19217>\
**Category:** Bear Web\
**Tags:** bug\
**Created:** [June 10, 2026, 7:51am UTC](https://community.bear.app/t/web-beta-issue-with-korean-input-and-spacebar-registration-on-windows/19217 "2026-06-10T07:51:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hyc9002](https://avatars.discourse-cdn.com/v4/letter/h/e36b37/32.png) [@hyc9002](https://community.bear.app/u/hyc9002)\
**Post date:** [June 10, 2026, 7:51am UTC](https://community.bear.app/t/web-beta-issue-with-korean-input-and-spacebar-registration-on-windows/19217/1 "2026-06-10T07:51:38Z")

</div>

Hello Bear Team,

First of all, thank you for releasing the Web version beta! I have been really enjoying it on Windows, but about a month ago, I started experiencing an annoying bug with Korean (IME) text input.

**[Environment]**

- **OS:** Windows

- **Platform:** Bear Web Version (Beta)

**[Issue Description]** When typing in Korean, the spacebar does not register properly on the first press immediately after a character is formed.

For example, if I want to type **“가 나”** (Ga [Space] Na):

1. I type **“가”**.

2. I press the spacebar once.

3. _Expected:_ A space should be inserted, resulting in "가 ".

4. _Actual:_ Nothing happens visually (it seems the first spacebar press only concludes the Korean IME composition).

5. I have to press the spacebar a **second time** to finally get a space.

It seems like the editor is swallowing the first spacebar event because it is recognizing it as the end of the IME composition character block, rather than inserting an actual space character.

Since it began around a month ago, it might be related to a recent update in the web beta. Could you please look into how the editor handles the `CompositionEnd` event and spacebar inputs for IME users?

Thank you!

---

<div class="post-metadata">

**Author:** ![rexikan](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/rexikan/32/4117_2.png) [@rexikan](https://community.bear.app/u/rexikan)\
**Post date:** [June 10, 2026, 12:33pm UTC](https://community.bear.app/t/web-beta-issue-with-korean-input-and-spacebar-registration-on-windows/19217/2 "2026-06-10T12:33:57Z")

</div>

Thanks for reporting. Will investigate.

---

<div class="post-metadata">

**Author:** ![rexikan](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/rexikan/32/4117_2.png) [@rexikan](https://community.bear.app/u/rexikan)\
**Post date:** [June 15, 2026, 5:47am UTC](https://community.bear.app/t/web-beta-issue-with-korean-input-and-spacebar-registration-on-windows/19217/3 "2026-06-15T05:47:52Z")

</div>

Bug fixed, and will be deployed later this week. You are right about the timing, the bug was introduced when fixing another IME bug on Safari.