693338 - Typing on dartlang.org doesn't work in Fennec

Status: RESOLVED DUPLICATE of bug 746769

(Firefox for Android Graveyard :: Keyboards and IME, defect)

Description

[(no longer active)]

Go to the URL, focus the editable area, and try typing something in.  Nothing happens.

Comment 1

[Aaron Train [:aaronmt]]

Reproducible on Nightly (10/17). Also getting some crazy checker boarding occurring as you begin to type.

Comment 2

[Martijn Wargers (dead)]

I can reproduce this on my EEE Transformer, using the latest nightly build.
When I press backspace or return, the typed characters suddenly appear.

Comment 3

[Martijn Wargers (dead)]

This might be related to bug 681421.

Comment 4

[Chris Peterson [:cpeterson]]

I can reproduce this on Native Fennec. Pressing backspace or return reveals the typed characters, but the first or last character is often missing.

Comment 5

[Chris Lord [:cwiiis]]

Possible dupe of bug #728983 ?

Comment 6

[Chris Peterson [:cpeterson]]

> Possible dupe of bug #728983 ?

No. This is strictly an IME bug.

Comment 7

[Brad Lassey [:blassey] (use needinfo?)]

what is the behavior on desktop with IME input? If not, how does the events sent by desktop's IME impl differ from Android's?

Comment 8

[Chris Peterson [:cpeterson]]

Mac IME has the same problem.

Comment 9

[Chris Peterson [:cpeterson]]

I am moving this bug to Core product because Mac Firefox does not display the composition string when using Mac's built-in IME. (I don't have access to Windows or Linux to test Firefox on those platforms).

Mac Chrome and Safari correctly display the composition string when using Mac's built-in IME.

Comment 10

[Mark Finkle (:mfinkle) (use needinfo?)]

Can we get some data on how this works on stock and chrome browsers? Include looking at etherpad and google docs, which are also content-editable apps.

Comment 11

[JP Rosevear [:jpr]]

Ehsan, can you take an initial look at this?  Believed to be a content editable problem.

Comment 12

[Chris Peterson [:cpeterson]]

dartlang.org editor works correctly on ICS stock browser, ICS Chrome Beta, Mac Chrome, and Mac Safari, BUT NOT Mac Firefox or Fennec.

Etherpad editor works correctly on ICS stock browser, ICS Chrome Beta, Mac Chrome, Mac Safari, and Mac Firefox. Etherpad has some problems on Fennec that should probably be a different bug.

Comment 13

[Martijn Wargers (dead)]

Removing qawanted as comment 12 seems to answer the questions in comment 10.
Please readd the qawanted keyword if more info is needed.

Comment 14

[(no longer active)]

Turning on the IME logging in the Java front-end code shows that Gecko does receive the IME event and calls back Java with notifyIMEChange and the updated text, so the bug here is probably a Fennec bug.

Comment 15

[(no longer active)]

So here's what this page does.  When you click on the editable area, it focuses the invisible textarea element it has, and it sets up a keydown event listener on that textarea in order to read the input text.  Once it receives the input text, it updates the div which overlays the textarea which provides rich text formatting (keyword highlighting, etc.)  This div as the class name "db-scroll-x-container", and includes one div per line as a child, plus another div with the class "db-caret" which simulates the caret that you see.  Hope this is useful to debug what's going wrong here.

Comment 16

[(no longer active)]

Filed bug 746769 for the Mac IME bug on this page.

Comment 17

[Chris Peterson [:cpeterson]]

I see that Fennec is receiving key events from Android and Gecko. Fennec is getting the correct text back from Gecko, but does not seem to be updating the textarea.

Comment 18

[(no longer active)]

(In reply to Chris Peterson (:cpeterson) from comment #17)
> I see that Fennec is receiving key events from Android and Gecko. Fennec is
> getting the correct text back from Gecko, but does not seem to be updating
> the textarea.

The textarea is not visible on the screen.  It is the "db-scroll-x-container" div which contains the elements representing the text, and the page js code keeps those contents updated.

Note that whatever goes wrong here is "fixed" if you press backspace.  Try inputting a few characters immediately followed by a backspace.