with MSIME on Facebook doesn't work well in Japanese environment

Fixed, flighted Issue #9876373

Details

Author
Yoshihisa O.
Created
Nov 19, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 7 people

Sign in to watch or report this issue.

Steps to reproduce

Updated Repro steps form another bug:
Description: 1. Go to facebook.com

  1. In the comment field, turn on Japanese IME.
  2. Try to type some text, such as “Toyota” and convert to one of Japanese by pressing spacebar and Enter key,. and add Japanese period.
  3. Type more text (ie: Kawasaki) with Japanese period.
  4. Delete text with backspace, or select the text to delete.
  5. Repeat step 3- 5.

Result:
Suddenly, additional text that were deleted before shows up.
After that, you can’t delete the extra text that showed up. Only way to remove unwanted text is to refresh the page.

input a comment on Facebook with MSIME behave annoying. If I remove my input by backspace key then input correctly, the wrong input return the textbox. and then remain input, cursor move to unexpected place.

https://youtu.be/ecz7IXT3qDI

It happens on
build 14971
Anniversary with latest update.

Please see other feedbacks in userfeedback VSO for feedbacks that are tracked by this work item.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To from “Brad E.” to “Nirankush P.”

      Changed Assigned To from “Nirankush P.” to “Grisha L.”

    • Could you please provide exact repro steps? I am not able to repro.

    • Microsoft Edge Team

      Changed Steps to Reproduce

      Changed Status to “Confirmed”

      Changed Steps to Reproduce

    • Do you need extra info or enough the steps that updated?

    • Microsoft Edge Team

      Changed Assigned To from “Grisha L.” to “Siye L.”

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

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

    • 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