Closed Bug 735806 Opened 12 years ago Closed 4 years ago

Input event fired twice when entering text with the virtual keyboard


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



(blocking-fennec1.0 -)

Tracking Status
blocking-fennec1.0 --- -


(Reporter: martijn.martijn, Unassigned)




(Keywords: testcase)


(1 file)

Attached file testcase
See testcase, steps to reproduce:
- With the vkb, type a letter, for example, 'a'.

Expected result:
- Under the input, 1 line of text should appear: 
event fired: input - input value: a

Actual result:
- Under the input, 2 lines of text appears:
event fired: input - input.value: 
event fired: input - input.value: a
I can reproduce this on my Galaxy S II.
blocking-fennec1.0: --- → ?
Assignee: nobody → cpeterson
blocking-fennec1.0: ? → +
mw22, what device were you testing? I suspect this bug might be a dupe of or related to bug 630576.
Tested on the Galaxy Nexus, Android 4.0.2.

I've added a dependancy, bug 630576 sure is related, although I don't know what would happen with this bug when that bug is fixed.
Depends on: 630576
So what is the impact of this bug? Finkle, do you remember why it was marked blocking?
blocking-fennec1.0: + → ?
if anyone finds a site that this breaks, please re-nom
blocking-fennec1.0: ? → -
No longer depends on: 630576
Priority: -- → P3
Assignee: cpeterson → nobody
Forgot to mention, click on the search input at the top of the page and you'll see a search overlay. Start typing in that overlay and you'll see letters appearing multiple times.
BM are you using prerelease versions of Firefox for Android (Aurora/Nightly)? Your comment sounds like bug 1133802.
@Kevin, I'm using 36.0.1.
Also, duplicate letters is one side effect of this bug I think. The real issue is the input event being fired twice. I checked it with console.log ;)
I found the bug described by BM in 37.0.1 and 38.0 (beta).

Trying to write "abcde" in the search box of any Wikimedia site would display this (successively):
a : a
b : aab
c : aabc
d : aabcabcd
e : aabcabcde
The problem I mentioned above is gone now, with 37.0.1 and current 38.0 beta.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly]( an issue can be reported at the [Fenix GitHub project]( If you want to discuss your report please use [Mozilla's chat]( server and join the [#fenix]( channel.
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.