Closed Bug 478882 Opened 11 years ago Closed 11 years ago

[TSF] MS Natural Input 2002 V8.1 is automatically turned on when editor gets focus

Categories

(Core :: Widget: Win32, enhancement)

x86
Windows XP
enhancement
Not set

Tracking

()

RESOLVED INVALID

People

(Reporter: masa141421356, Unassigned)

References

Details

(Keywords: relnote, Whiteboard: [relnote: only Gecko 1.9.2a1 or later, and also not affected by default till Bug 478029 is fixed])

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090211
Minefield/3.2a1pre
Built from http://hg.mozilla.org/mozilla-central/rev/784122b49e33+

Windows XP SP3 Japanese

When using some IME, IME is automatically turned on when editor gets focus.

Reproduced:     Microsoft Natural Input 2002 ver.8.1
NOT reproduced: Microsoft IME Standard 2002 ver.8.1
NOT reproduced: Microsoft Natural Input 2003
NOT reproduced: Microsoft IME Standard 2003
Summary: [TSF] some IME is automatically turned on when editor gets focus. → [TSF] some IMEs are automatically turned on when editor gets focus
I guess that MS Natural Input 2002 sets the IME state per ITfContext. Maybe, we need a hacky implementation of nsTextStore...
I think this should not block bug 478029, this should be an enhancement bug excepting that my idea is wrong.
No longer blocks: 478029
Severity: normal → enhancement
ok, Kimura-san found a kb in MS.
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=295373

That said this issue is a bug of MS Natural Input 2002. I bet we cannot fix this bug without hacky way. But hacky implementation may break other text services behavior. So, we should not fix this bug.

But we should document this issue to release note.

-> INVA
Status: NEW → RESOLVED
Closed: 11 years ago
Keywords: relnote
Resolution: --- → INVALID
Summary: [TSF] some IMEs are automatically turned on when editor gets focus → [TSF] MS Natural Input 2002 V8.1 is automatically turned on when editor gets focus
Whiteboard: [relnote: only Gecko 1.9.2a1 or later, and also not affected by default till Bug 478029 is fixed]
You need to log in before you can comment on or make changes to this bug.