Modifying the DOM of a contenteditable element during a compositionend event listener causes the element to stop receiving future composition events.

Fixed Issue #10744195


Jan 31, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Step 1: Open and dev tools (to see console messages)
Step 2: Set keyboard to use a composing IME. As an example, we’ll use the Korean Hangul Microsoft IME.
Step 3: Type ‘g’ in the body.

At this point, ‘start’ and ‘end’ should have printed in the console. The content of the body should have cleared.

Step 4: Attempt to type ‘s’ in the body.

Result: No composition appears and compositionstart/compositionend events no longer get fired for the body.

Expected result: Compositions should work as usual, with the start/end events firing.

Note that this also happens for modifying the DOM via innerHTML. This does not reproduce on IE 11, Chrome 55 or Firefox 50.


0 attachments

    Comments and activity

    • Sorry, step 1 should be:
      Step 1: Open and dev tools (to see console messages)

    • Ah, the jsfiddle autolinking doesn’t seem to respect markdown.

      The link is:

      The dev tools should then be opened to see console messages.

    • Microsoft Edge Team

      Changed Status to “Fixed”

    You need to sign in to your Microsoft account to add a comment.

    Sign in