WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#18454 closed defect (bug) (fixed)

Pressing backspace twice during input in Japanese IME mode will delete everything afterward in the block

Reported by: tai Owned by:
Milestone: 3.3 Priority: normal
Severity: critical Version: 3.2.1
Component: TinyMCE Keywords:
Focuses: Cc:

Description

The TinyMCE versin 3.4.2 used in WP 3.2.1 might have a big problem for Japanese Windows users, so please update to the latest one.

Copied from the report to the bug tracker of tinymce.com:

http://www.tinymce.com/develop/bugtracker_view.php?id=4320


Description:

Description of problem:

When using the Windows IME input mechanism to type in Japanese text into a TinyMCE editor, pressing backspace twice deletes everything after the cursor in a block level element. For example, if I start typing Japanese text at the beginning of an existing paragraph, press delete twice, the entire paragraph disappears after the cursor! This is an Internet Explorer thing only. Haven't tested i.e.9. Tested on Windows 7. Tested on Windows 7 JA using Internet Explorer 8 JA edition.

Steps to reproduce:

  1. create a paragraph - type the word "text" in the TinyMCE editor.
  2. enable the Japanese IME and type in three characters before the word "text".
  3. Don't exit the IME mode - just press delete twice after the characters have been typed.
  4. The word "text" will then be deleted.

Expected result:
that just two japanese characters get deleted

Actual result:
all text in an element block (such as text inside a newly created <p> tag) will be deleted that comes after the cursor.

Change History (3)

comment:1 ocean903 years ago

Related #18107

comment:2 azaozz3 years ago

  • Milestone changed from Awaiting Review to 3.3
  • Resolution set to fixed
  • Status changed from new to closed

Should be fixed in [18660], feel free to reopen if that still happens.

comment:3 tai3 years ago

Thank you!

I've tried turnk, and found the problem fixed.

Note: See TracTickets for help on using tickets.