Closed Bug 1110884 Opened 10 years ago Closed 9 years ago

Plugin IME broken on OS X 10.7 and 10.6 in non-e10s mode

Categories

(Core :: Widget: Cocoa, defect)

All
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
e10s m6+ ---
firefox37 + fixed
firefox38 + fixed

People

(Reporter: smichaud, Assigned: smichaud)

References

Details

As of landing the patch for bug 1092630, plugin IME no longer works on OS X 10.7 and 10.6 (the lowest two major versions of OS X we still support), even in non-e10s mode.  When you try to do IME input in a plugin's text field on those versions of OS X, whatever you type appears directly in the text field (and no IME pops up).

For more information see bug 1092630 comment #51.

This is probably because, as of bug 1092630, we use synthetic keyboard events to process plugin keyboard input.  By reverse engineering the OS, I already found a workaround for this (and other problems), but it only works on OS X 10.8 and up.  I'd need to cover the same ground again, but this time on OS X 10.7 and below, to find a different workaround.

I'm probably the only one in Mozilla who can do this.  But I'm not sure when I'll have time for it, so I'm leaving this bug unassigned (at least for the time being).
[Tracking Requested - why for this release]:

Though probably not a showstopper, this is a serious problem.  How serious it is depends on how many people using Chinese, Japanese or Korean are still on OS X 10.7 and below.  Probably the only way to find out is to see how many people complain :-(
Blocks: e10s-plugins
Summary: Plugin IME broken on OS X 10.7 and 10.6 → Plugin IME broken on OS X 10.7 and 10.6 in non-e10s mode
Assignee: nobody → davidp99
No longer blocks: e10s-plugins
Bug 1110888 can supercede this bug.  I'm investigating it as an alternative to this bug.
Depends on: 1110888
I'm going to work on bug 1110888 first, and only fall back to this bug if that doesn't work out.
Assignee: davidp99 → smichaud
Blocks: e10s-plugins
This is fixed by the patch for bug 1110888, which just landed on mozilla-inbound and mozilla-aurora.  It should get onto mozilla-central in the next 24 hours.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.