537436 - Backspace when IME editor is active causes Camino to go back to previous page on Facebook

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: General, defect)

Description

[Ambrose Li]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en; rv:1.9.0.16) Gecko/2009120123 Camino/2.0.1 (MultiLang) (like Firefox/3.0.16)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en; rv:1.9.0.16) Gecko/2009120123 Camino/2.0.1 (MultiLang) (like Firefox/3.0.16)

When typing Chinese or Japanese, if there is a mistyped radical (i.e., when the word is still not in the process of being composed), backspacing should just erase the mistyped radical. However, pressing Backspace at this point does not even erase the current input, but causes Camino to go back to the previous page and erase everything that has been entered on the form. This is disastrous for Chinese and Japanese users and makes Camino completely unusable for Chinese or Japanese.

Reproducible: Always

Steps to Reproduce:
1.Make sure some page is loaded (i.e., so that the Back button has a page to go back to)
2.Go to some page with a form (e.g., facebook),
3.Switch input to Chinese or Japanese
4.Type something but do not hit the convert key (space) yet
5.Hit Backspace
Actual Results:  
Camino goes back to the previous page in step 1

Expected Results:  
Nothing should happen. The convert key hasn't even been hit. Every keystroke should be interpreted by the IME editor, especially some key that obviously should be interpreted by the IME editor like Backspace.

I don't remember seeing this with Camino 2.0 or any previous versions. This is a new bug for Camino 2.0.1.

This only affects input systems that requires an IME editor. This does not affect, for example, English, Hebrew, or Arabic

Comment 1

[Ambrose Li]

Sorry, this seems to only affect facebook. Probably a Facebook bug.

Comment 2

[Chris Lawson (gone)]

If you can come up with a reduced testcase, it might be worth kicking this to TE so that Facebook can fix it. They're probably doing something weird with Javascript that's causing this.

Ilya, any idea how this might be happening?

Comment 3

[philippe (part-time)]

Does the same problem happens with Firefox 3.0.xx (or newer) ?

(Firefox 3.0.xx is equivalent to Camino 2.0 - Gecko 1.9.0).

Comment 4

[Chris Lawson (gone)]

Ambrose, is this still happening? And if so, can you answer comment 3?

Comment 5

[Chris Lawson (gone)]

INCOMPLETE absent answers to the pending questions.