fix Korean(and Chinese, Japanese) IME behavior (#4541)

[ioklo]

Hello, this PR is for issue #4541 - Korean characters problem

• fix displaying Korean letters twice during composition
• show composition letters between the text not over the text

Doing so, I added ICompositionEvent that has 'data' field. On 'compositionupdate' events, textarea is changed by composition data.

To show composition letters between the text, the visibleRange is calculated every compositionupdate event with composition word. It can be expensive.

I changed the variable shouldEmptyTextArea to be always true because I think textarea should be empty when composition starts but I didn't test with other browsers (How?).

Symptom (VSCode v1.0, type 'dkssudgktpdy')

Expected (there are two cursors.. it must be fix either)

And When I composite letters between the text, the letters are displayed over the text. But Korean IME doesn't act like that. (type 'gksrmf')

Expected

It is confused that Japanese IME usually show composition letters over the text (in the notepad) but when I tested with Microsoft Word, the composition letters are occupied between the text. (type 'sensei')

After change

But It's same as Microsoft Word

[mention-bot]

By analyzing the blame information on this pull request, we identified @alexandrudima, @egamma and @joaomoreno to be potential reviewers

[msftclas]

Hi @ioklo, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

[msftclas]

@ioklo, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, MSBOT;

[alexdima]

@ioklo Thank you very much for this change! ❤️

Based on a few issues and on this description I was able to put together an IME Smoke test that we will go through from now on any time we make changes in the input handling and your changes make VSCode work like Word in these test cases!