Details
-
Bug
-
Resolution: Fixed
-
Low
-
2
-
Severity 2 - Major
-
Description
This is a bug introduced in Chrome 65. According to https://bugs.chromium.org/p/chromium/issues/detail?id=829224 and https://bugs.chromium.org/p/chromium/issues/detail?id=826615, this bug is resolved in Chrome 67.0.3387.0. Target stable release for Chrome 67 is May 29 (https://www.chromium.org/developers/calendar).
We have confirmed the bug is fixed in current Canary version (67.0.3390.0).
Summary
Japanese IME normally enters multiple letter combination entry state to express consonant+vowel letter such as "k" + "i" = "き", however the first consonant letter ( "k", in this example) is auto-committed in the Confluence editor, so the Japanese IME cannot enter the combination entry.
Environment
Client that runs the browser is
- Windows and macOS
- Chrome (Tested with ver. 65.0.3325.162)
- Microsoft IME (Japanese) , Google Japanese IME, and Mac IME (Japanese) (This means this occurs in any IME.)
Steps to Reproduce
- Create a blank page and add elements as below.
- Add a table.
- Set IME to Japanese.
- Type two letters in a cell (Consonant + Vowel)
e.g.) Type "k"(Consonant) + "i"(Vowel). - Type No.4 letters again in a cell next to the No.4 cell
e.g.) Type "k"(Consonant) + "i"(Vowel).
Expected Results
"k" + "i" should be always converted to "き". ("ki" = "き" in Japanese)
Firefox.mov
Actual Results
"k" + "i" becomes "kい". The initial consonant letter is auto-committed. ("i" = "い" in Japanese)
GoogleIME.mov
MicrosoftIME.mov
Notes
- Please note this symptom is different from the issue
CONFSERVER-54326because it reports that first letter is "ignored" while the letter is "auto-committed" in this case. - This occurs only at the Chrome environment, and IE11 also has another issue(Cannot type double byte characters in Section through IE11). Firefox works fine.
- As long as crawling the web and testing, this is apparently coming from a common malfunction of Chrome v65.x, however it is suspected any implementation on the Confluence is triggering the malfunctioning.
- Evidences for the above statement are as below.
- This has not occurred on Chrome v63.x and prior.
- There are related articles outside Atlassian product,
- Latest Chrome 65 update breaks start of CJK IME input · Issue #2009 · quilljs/quill · GitHub
- 576573 - Japanese IME: First character is auto-committed on office extensions - chromium - Monorail (This is a bit old report, however still opened.)
- Google Groups – Chrome 65 アップデート後 Slack で一文字目が意図せず確定される問題について
Workaround
- Delete the affected letter, and re-type the contents.
- Add an empty space before typing the first letter.
- Use Firefox browser.
Attachments
Issue Links
- is cloned from
-
CONFSERVER-55177 Unable to type Japanese characters correctly in a table with Chrome 65+ in case that the more left cell is not empty
- Closed