730478 - element.value returns an empty string after text is input

Status: RESOLVED DUPLICATE of bug 735469

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

Description

[:Margaret Leibovic]

This is breaking form autocomplete, since we can't filter the suggestions. This is the line that's failing:

http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/browser.js#2831

Chris, I'm cc'ing you, since alexp worked on some of these input-related issues. I'm not sure who else would be able to help with this problem.

Comment 1

[:Margaret Leibovic]

Hm, actually, I found this works on some forms. However, it is still a problem on:
http://people.mozilla.org/~mwargers/tests/autocomplete_forms/textinput_form.html

Comment 2

[Chris Peterson [:cpeterson]]

Having form autocomplete work seems pretty important, since typing on the VKB is cumbersome. :)

Comment 3

[Chris Peterson [:cpeterson]]

This bug is may be related to bug 630576 (Fennec should send key events to content).

Comment 4

[Doug Turner (:dougt)]

chris, is this a bug you can pick up?

Comment 5

[Chris Peterson [:cpeterson]]

OK. I think this bug is related to bug 630576, which may be an invasive core change. I will investigate.

Comment 6

[Chris Peterson [:cpeterson]]

Triage, this bug needs a priority.

Comment 7

[JP Rosevear [:jpr]]

Beta blocking because form sync is also a beta blocker.

Comment 8

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

(In reply to Margaret Leibovic [:margaret] from comment #0)
> This is breaking form autocomplete, since we can't filter the suggestions.
> This is the line that's failing:
> 
> http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/
> browser.js#2831
> 
> Chris, I'm cc'ing you, since alexp worked on some of these input-related
> issues. I'm not sure who else would be able to help with this problem.

is this an uncommitted composition?

Comment 9

[Chris Peterson [:cpeterson]]

> http://people.mozilla.org/~mwargers/tests/autocomplete_forms/textinput_form.html

margaret, what is the expected autocomplete behavior and what are you actually seeing? Which device are you testing?

On my Galaxy S II, autocomplete seems to work correctly, though I get an unfiltered autocomplete box with all possible suggestions *before* I type anything. I don't expect the suggestion list until after I start typing.

On my Galaxy Nexus, the autocomplete menu does not filter the suggestion list until I enter a space.

Comment 10

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

(In reply to Chris Peterson (:cpeterson) from comment #9)

> On my Galaxy S II, autocomplete seems to work correctly, though I get an
> unfiltered autocomplete box with all possible suggestions *before* I type
> anything. I don't expect the suggestion list until after I start typing.

The unfiltered list is by design. We want "less typing", so we show the list right away.

Comment 11

[Chris Peterson [:cpeterson]]

I am duping this bug with Galaxy Nexus-specific bug 735469. In IRC, margaret confirmed that these are the same problem.