In Korean, althogh foucsout to textbox, It still has focus.

Fixed Issue #8471287


Aug 12, 2016
This issue is public.
Found in
  • Microsoft Edge
Fixed in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

  • Typing character in KOREAN to textbox
  • Click empty space outside of textbox(focus out)
  • Typing any character quickly
  • textbox still has focus and display character

Check out this bin
And attached video.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

    Changed Assigned To to “Bogdan B.”

  • The page causes another hilarious bug on Edge.

    1. Type any Korean character on the textbox by touch
    2. Tap to select any text on the top side of the textbox
    3. Type any Korean character by touch
    4. OMG DOM gets modified???


  • Also, following your steps causes page crash on GitHub issue page.

  • The issue looks quite serious, but I cannot reproduce on a non-korean virtual keyboard, so my guess is that the problem lies in the Korean keyboard, not Edge.

    That being said, how it is even allowed for the keyboard to modify a non-contentEditable area of the dom is a question we should try to understand. I’m moving this bug to the Text Input and Editing team for them to figure out how this behavior is possible and how to make it impossible in the future (independtly of the fact the korean keyboard should not attempt to do this).

    This last part seems like a bug we could fix. It would probably prevent the crashes, too, since we would simply reject the invalid requests.

    Here is the video again, just in case:

  • Microsoft Edge Team

    Changed Assigned To to “Amit J.”

    Changed Assigned To from “Amit J.” to “Amit J.”

    Changed Status to “Confirmed”

    Changed Assigned To from “Amit J.” to “Siye L.”

    Changed Status from “Confirmed” to “In code review”

    Changed Status from “In code review” to “Fixed”

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Insider Preview build.

    Best Wishes,
    The MS Edge Team

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

Sign in