# FIX: Word limit shouldn't break IME composition

**URL:** https://meta.discourse.org/t/fix-word-limit-shouldnt-break-ime-composition/400178
**Category:** Bug
**Tags:** fixed
**Created:** [April 8, 2026, 3:16am UTC](https://meta.discourse.org/t/fix-word-limit-shouldnt-break-ime-composition/400178 "2026-04-08T03:16:46Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![small-lovely-cat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/small-lovely-cat/32/553546_2.png) [@small-lovely-cat](https://meta.discourse.org/u/small-lovely-cat)
#### Post date: [April 8, 2026, 3:16am UTC](https://meta.discourse.org/t/fix-word-limit-shouldnt-break-ime-composition/400178/1 "2026-04-08T03:16:46Z")

</div>

There exists a bug in discourse boost composer.

For IME using language, like Chinese, the original logic will stop the IME composition when the word is near the limit, causing the bug shown in the figure.

This commit stops the cut when user is composing, while call the cut process after that.

Before:

[https://github-production-user-asset-6210df.s3.amazonaws.com/77799160/575044933-75445120-e20c-4858-b316-5bd6bc541ac3.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260806%2Fus-east-1%2Fs3%2Faws4\_request&X-Amz-Date=20260806T101139Z&X-Amz-Expires=300&X-Amz-Signature=71cabee184fce6ece6f758ef34a1c745663c21ca5093b4f2c0157260b6b3a242&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4](https://github-production-user-asset-6210df.s3.amazonaws.com/77799160/575044933-75445120-e20c-4858-b316-5bd6bc541ac3.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260806%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260806T101139Z&X-Amz-Expires=300&X-Amz-Signature=71cabee184fce6ece6f758ef34a1c745663c21ca5093b4f2c0157260b6b3a242&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4)

After:

[https://github-production-user-asset-6210df.s3.amazonaws.com/77799160/575044714-49e8cf55-0573-47e8-8861-54e9ea8d4b05.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260806%2Fus-east-1%2Fs3%2Faws4\_request&X-Amz-Date=20260806T101140Z&X-Amz-Expires=300&X-Amz-Signature=5e6414dc89db3ab03481e5bbfed7906833d8d34c5f2802c5d4414d31bd729d52&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4](https://github-production-user-asset-6210df.s3.amazonaws.com/77799160/575044714-49e8cf55-0573-47e8-8861-54e9ea8d4b05.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260806%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260806T101140Z&X-Amz-Expires=300&X-Amz-Signature=5e6414dc89db3ab03481e5bbfed7906833d8d34c5f2802c5d4414d31bd729d52&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4)

A PR is raised here:

> <https://github.com/discourse/discourse-boosts/pull/1>
>
> There exists a bug in discourse boost composer.
> 
> For IME using language, like …Chinese, the original logic will stop the IME composition when the word is near the limit, causing the bug shown in the figure.
> 
> This commit stops the cut when user is composing, while call the cut process after that.
> 
> Before:
> 
> https://github.com/user-attachments/assets/75445120-e20c-4858-b316-5bd6bc541ac3
> 
> After:
> 
> https://github.com/user-attachments/assets/49e8cf55-0573-47e8-8861-54e9ea8d4b05

---

<div class="post-metadata">

### Author: ![small-lovely-cat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/small-lovely-cat/32/553546_2.png) [@small-lovely-cat](https://meta.discourse.org/u/small-lovely-cat)
#### Post date: [June 23, 2026, 5:39am UTC](https://meta.discourse.org/t/fix-word-limit-shouldnt-break-ime-composition/400178/2 "2026-06-23T05:39:38Z")

</div>

It seems this PR is stale, maybe take time to see that?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 23, 2026, 6:09am UTC](https://meta.discourse.org/t/fix-word-limit-shouldnt-break-ime-composition/400178/3 "2026-06-23T06:09:27Z")

</div>

thanks for reminding us let me prioritize this so the team will have a look

---

<div class="post-metadata">

### Author: ![nat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nat/32/235063_2.png) [@nat](https://meta.discourse.org/u/nat)
#### Post date: [June 23, 2026, 10:22am UTC](https://meta.discourse.org/t/fix-word-limit-shouldnt-break-ime-composition/400178/5 "2026-06-23T10:22:28Z")

</div>

Thanks for your contribution! I’ve merged the PR.

---

<div class="post-metadata">

### Author: ![nat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nat/32/235063_2.png) [@nat](https://meta.discourse.org/u/nat)
#### Post date: [June 27, 2026, 12:00am UTC](https://meta.discourse.org/t/fix-word-limit-shouldnt-break-ime-composition/400178/6 "2026-06-27T00:00:13Z")

</div>

This topic was automatically closed after 3 days. New replies are no longer allowed.
