Closed Bug 1206387 Opened 9 years ago Closed 8 years ago

[TSF] candidate box may be interrupted when appendChild

Categories

(Core :: Widget: Win32, defect, P4)

43 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla50
Tracking Status
firefox43 --- affected
firefox-esr45 --- affected
firefox50 --- fixed

People

(Reporter: yfdyh000, Unassigned)

References

Details

(Keywords: inputmethod, Whiteboard: tpi:+)

Attachments

(1 file)

Attached file testcase
Steps to reproduce:
See testcase.

The testcase refined and modified from https://www.firefox.net.cn/res/js/dev/windeditor/windeditor.js?v=20140228, a Chinese forum, powered by phpwind v9.0.


Actual results:
This problem will appear on the forum's advanced editor (https://www.firefox.net.cn/bbs-post-reply?tid=51193, registration required), the users will cannot use the input method to input Chinese. non-IME is normal.

If disabled the intl.tsf.enable in about:config, the problem does not occur.

Chrome 45 and IE 11 is normal.


Expected results:
IME's candidate box does not flash and is closed.
IE 11 is NOT normal.

IE 11 and Edge both have the same bug. Only Chrome works normal.
(In reply to Benjamin Peng from comment #1)
> IE 11 is NOT normal.
> 
> IE 11 and Edge both have the same bug. Only Chrome works normal.

QQPinYin 4.7 and Microsoft PinYin with IE 11 on Win8.1 works fine for me.


Also, typed characters are reserved for Microsoft PinYin with IE 11, are canceled for QQPinYin 4.7 with IE 11.
(In reply to YF (Yang) from comment #2)
> (In reply to Benjamin Peng from comment #1)
> > IE 11 is NOT normal.
> > 
> > IE 11 and Edge both have the same bug. Only Chrome works normal.
> 
> QQPinYin 4.7 and Microsoft PinYin with IE 11 on Win8.1 works fine for me.
> 
> 
> Also, typed characters are reserved for Microsoft PinYin with IE 11, are
> canceled for QQPinYin 4.7 with IE 11.

Considering we don't have this problem on Win 7 at all, it's safe to presume that TSF's behavior does change with system versions. I'm on Win 10, it mean explain the difference.

To be more specific, what I encounter in Win 10 is: 

I tried Sogou IME and Microsoft Pinyin. None of them work perfectly in IE11, Edeg or Firefox. But the behavior is slightly different.

For Sogou, I can't type at all. All I typed will be erased instantly.

For MS PinYin, all I typed will be automatically considered "finished" (instead waiting me to choose the words) so essentially I can only type in Latin characters, not Chinese.

I also tried Japanese IME. For Microsoft's Japanese IME, the problem is worse in Firefox (hard to describe, but you can try it: totally unusable); In IE11/Eege it's much better but still very buggy (you can choose words but the pop-up menu disappears immediately).
Can you see this bug.
Flags: needinfo?(masayuki)
Sounds like that this is each IME's specific behavior. In TSF mode, we *need* to notify TSF of layout change. Then, active IME can do anything which wants. So, the most IMEs want to commit composition in this case.

FYI: Whether an IME is installed as IMM-IME or TSF-TIP may depend on the version of Windows. For example, Google Japanese Input installs itself as TSF-TIP only on Win8 or later since store apps work only with TSF.

I guess that the problems which you see can be reproduced on Wordpad and/or Microsoft Word when you resize their window.

> For Microsoft's Japanese IME, the problem is worse in Firefox (hard to describe, but you can try it:
> totally unusable);

This sounds too bad. Some IMEs may stop working when some notifications are notified during composition. MS-IME for Japanese may have this case or we might notify TSF of layout change during document lock (although, such bugs should be fixed on 41, we put off enabling TSF mode from 40 to 41 for waiting such bug fixes).
Flags: needinfo?(masayuki)
(In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) (Offline: 9/21-23, prehaps, not so active: 9/24, 9/25) from comment #5)
> Sounds like that this is each IME's specific behavior. In TSF mode, we
> *need* to notify TSF of layout change. Then, active IME can do anything
> which wants. So, the most IMEs want to commit composition in this case.
> 
> FYI: Whether an IME is installed as IMM-IME or TSF-TIP may depend on the
> version of Windows. For example, Google Japanese Input installs itself as
> TSF-TIP only on Win8 or later since store apps work only with TSF.
> 
> I guess that the problems which you see can be reproduced on Wordpad and/or
> Microsoft Word when you resize their window.
> 
> > For Microsoft's Japanese IME, the problem is worse in Firefox (hard to describe, but you can try it:
> > totally unusable);
> 
> This sounds too bad. Some IMEs may stop working when some notifications are
> notified during composition. MS-IME for Japanese may have this case or we
> might notify TSF of layout change during document lock (although, such bugs
> should be fixed on 41, we put off enabling TSF mode from 40 to 41 for
> waiting such bug fixes).

The behaviors may slightly different with different IMEs, but none of IME I tried works in Win 10 at least.. and it's including MS Japanese IME.
Do we have TSF tracking bug?
Blocks: 478029
Priority: -- → P4
Whiteboard: tpi:+
Confirmed fixed by bug 1224994.
Status: NEW → RESOLVED
Closed: 8 years ago
Depends on: 1224994
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: