facebookarchive/draft-js

Korean typing is so slow in Chrome browser

Open

#1102 opened on Mar 29, 2017

View on GitHub
 (8 comments) (0 reactions) (1 assignee)JavaScript (22,554 stars) (2,646 forks)batch import
IMEbughelp wanted

Description

Do you want to request a feature or report a bug? bug

What is the current behavior? Korean typing is so slow and lagging in Chrome browser. (Firefox & Safari is OK)

Especially, if you hold pressing the backspace key to erase a character, it seems that it does not work properly. It looks like doing nothing.

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: **

You can see: https://youtu.be/gnLmiaw7Sf0

The sequence is 'typing and pressing back space. English and Korean with same sequence. English is erased smoothly but Korean is very very slow.

It is tested at https://draftjs.org/

What is the expected behavior?

Works same as English.

Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?

It is tested at https://draftjs.org/ Probably latest version.

Contributor guide

Tech stack
javascriptreact
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of Draft.jsFamiliarity with ReactUnderstanding of browser event handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the handling of composition events in Draft.js, particularly in the Editor component. Check the Chrome specific behavior for Korean IME. Look at existing code in `src/component/handlers/editOnCompositionStart.js` and related files. Review the issue comments for any reported workarounds or findings.