[OOPP] Input Mehtod doesn't work on out-of-process plugins of GTK+

RESOLVED INCOMPLETE

Status

()

Core
Plug-ins
--
major
RESOLVED INCOMPLETE
7 years ago
11 months ago

People

(Reporter: jing, Unassigned)

Tracking

({inputmethod})

Trunk
x86_64
Linux
inputmethod
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: Firefox3.6.10 on Ubuntu10.10 & firefox 4 (4.0b12pre(2011-02-13)) on Mac 10.6

Input a:あ to text field or a TLF compontent of a swf file playing with Flash player 

RESULT: Roman A  was inputted.

EXPECTED: Japanese HIRAGANA あ is inputted. 

Reproducible: Always

Steps to Reproduce:
1.Input a:あ to text field or a TLF compontent of a swf file playing with Flash player 
Actual Results:  
RESULT: Roman A  was inputted.



Expected Results:  
EXPECTED: Japanese HIRAGANA あ is inputted. 

1) Anthy IME can input Japanese in Firefox4.
2) ATOK works fine in Firefox 3.6.3 on Ubuntu10.04, doesn't work in Firefox3.6.10 on Ubuntu10.10
3) It happens both TLF and Text Area component.
4) Mac10.6 has same bug in firefox 4. Windows works fine.

Updated

7 years ago
Keywords: inputmethod

Updated

7 years ago
Component: General → Plug-ins
Product: Firefox → Core
QA Contact: general → plugins
Summary: Can't input Japanese by using ATOK X3 IME with Firefox4 (4.0b12pre(2011-02-13))& Firefox3.6.10 on Ubuntu10.10 → [OOPP] Can't input Japanese by using ATOK X3 IME with Firefox4 (4.0b12pre(2011-02-13))& Firefox3.6.10 on Ubuntu10.10
Version: unspecified → Trunk

Comment 1

7 years ago
Tried reproducing the issue using the following website:
http://labs.adobe.com/technologies/textlayout/demos/

What I did:
1. Activated from IBus preferences, input method -  Japanese(anthy) and Arabic(kbd)
2.Entered website and started typing  

Results:

 - for Japanese the text isn't displayed correctly (see Screenshot 1) - issue present on all browsers - inclining to think that it is OS related
          1. The "a" character is displayed as small boxes
          2. Not all the characters are displayed as Japanese symbols 
          3. Roman letters are displayed multiple times although pressed just once.

 - for Arabic the text seems to be displayed correctly

Comment 2

7 years ago
Created attachment 519382 [details]
Screenshot 1

Comment 3

7 years ago
The fact that some roman characters are displayed also can be explained by reading the following article (sorry for mentioning it in Comment 1, but I do not speak Japanese):

http://newton.uor.edu/Departments%26Programs/AsianStudiesDept/Language/japanese_write.htm

Updated

7 years ago
Duplicate of this bug: 651841

Updated

7 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: [OOPP] Can't input Japanese by using ATOK X3 IME with Firefox4 (4.0b12pre(2011-02-13))& Firefox3.6.10 on Ubuntu10.10 → [OOPP] Input Mehtod doesn't work on out-of-process plugins of GTK+
Works for me on Mac. If this happens in other browsers on Ubuntu, I'm thinking this is OS-level.

George, can you confirm?
Status: NEW → UNCONFIRMED
Ever confirmed: false
Whiteboard: [invalid?]
(In reply to comment #5)
> Works for me on Mac. If this happens in other browsers on Ubuntu, I'm thinking
> this is OS-level.
> 
> George, can you confirm?

This is Linux.  Mac OOPP supports by Cocoa event model.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Created attachment 530477 [details]
Screenshot of "a:あ" GTK Flash Rendering

Here is a screenshot of how a:あ renders on a flash text field in Linux. FWIW, it displays exactly the same in Chromium (the only other flash-supported browser I could find).  I'm leaning towards this being an OS-level issue.

I've tried installing the Ubuntu Japanese language pack, using Japanese character encoding in Firefox, and even switching Firefox to a Japanese locale without any success. Nor was I successful doing the same under Chromium.

This MAY be OS-level...but I've exhausted my expertise.
Whiteboard: [invalid?]
Both of screenshots in comment #2 and comment #7 are not any softwares fault. The commenters should choose a correct font for Japanese characters.

Anyway the original report is another problem.  jing, did you test on 64bit Linux? If so, I could confirm this issue. If not, we need to investigate in further detail.

Comment 9

7 years ago
I got the same bug.

The bug is escaped by dom.ipc.plugins.enabled;false.

ibus-1.3.99.20110419-11.fc15.x86_64
ibus-mozc-1.1.758.102-2.fc15.x86_64
mozc-1.1.758.102-2.fc15.x86_64
libflashplugin.so: 11.0 d1 (x86_64)
Hardware: x86 → x86_64
(In reply to comment #9)
> libflashplugin.so: 11.0 d1 (x86_64)

The flash plugin is really for 64bit architecture? I supposed the plugin is 32bit and used with nsplugin wrapper or something like that.

Comment 11

7 years ago
(In reply to comment #10)
> (In reply to comment #9)
> > libflashplugin.so: 11.0 d1 (x86_64)
> 
> The flash plugin is really for 64bit architecture?
Yes.
64 bit plugin on 64 bit firefox.
Plugin is available from labs.adobe.com
(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #9)
> > > libflashplugin.so: 11.0 d1 (x86_64)
> > 
> > The flash plugin is really for 64bit architecture?
> Yes.
> 64 bit plugin on 64 bit firefox.
> Plugin is available from labs.adobe.com

Thanks for the info.

I could intput Japanese with the 64bit plugin but its behavior is very weird.

1) the biggest problem is that preedit string is not drawn at all.
2) I had to click on text area after Ctrl+Space (i.e. ibus is on)

The first one is a fault of flash plugin itself.

The second one is probably related to focus handling of firefox.  I guess Masayuki knows something.
(In reply to comment #12)
> (In reply to comment #11)
> > (In reply to comment #10)
> > > (In reply to comment #9)
> > > > libflashplugin.so: 11.0 d1 (x86_64)
> > > 
> > > The flash plugin is really for 64bit architecture?
> > Yes.
> > 64 bit plugin on 64 bit firefox.
> > Plugin is available from labs.adobe.com
> 
> Thanks for the info.
> 
> I could intput Japanese with the 64bit plugin but its behavior is very weird.
> 
> 1) the biggest problem is that preedit string is not drawn at all.
> 2) I had to click on text area after Ctrl+Space (i.e. ibus is on)

On my environment, the behavior is the same with dom.ipc.plugins.enabled = false.

Comment 14

7 years ago
During typing, the following message is shown:
(<unknown>:11433): Gdk-WARNING **: gdkdrawable-x11.c:952 drawable is not a pixmap or window

11433 means the process number for plugin-container.

Comment 15

11 months ago
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.