716444 - pressing tab to move to next input box erases the last word in previous text box

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect, P5)

Description

[donrhummy]

User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
Build ID: 20120104111157

Steps to reproduce:

entered information into a text box and hit the tab button on the virtual android keyboard


Actual results:

it erased the last word in the previous text box (if there's one whole word in that input box, the input box is cleared. if the's a word with a period in it, like an email address, everythingnafter the period is erased)


Expected results:

it should have left the input box alone and moved the cursor to the next box

Comment 1

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

Alex if this happens on a phone, please make sure we commit the composition when hitting next.

Comment 2

[Alex Pakhotin (:alexp)]

To: [e-mail]:
Can you provide a little more information please? What device and what virtual keyboard are you using? Does this happen on any website, which has a form, or just on some specific one?

Not many virtual keyboards have the Tab key - I've found the Tab only on the standard Android keyboard on a tablet, and Hacker's Keyboard, but I could not reproduce this issue with any of them. Tried on a couple of the phones as well.

The thing is - I don't quite get why it could happen. We send the composition events only when the edited text is being changed, there is no "open composition session", which needs to be committed.


Naoki, have you seen anything like this?

Comment 3

[donrhummy]

(In reply to Alex Pakhotin (:alexp) from comment #2)
> To: [e-mail]:
> Can you provide a little more information please? What device and what
> virtual keyboard are you using? Does this happen on any website, which has a
> form, or just on some specific one?

Any website.

> Not many virtual keyboards have the Tab key - I've found the Tab only on the
> standard Android keyboard on a tablet, and Hacker's Keyboard, but I could
> not reproduce this issue with any of them. Tried on a couple of the phones
> as well.

I'm using a Galaxy Tab 10.1
 
> The thing is - I don't quite get why it could happen. We send the
> composition events only when the edited text is being changed, there is no
> "open composition session", which needs to be committed.

I'm not sure why it's happening, but it's only if I use the Tab button to go to the next input box. If I click in the next input box it does not occur. Also, this does NOT occur in "Dolphin For Pad" (another browser for Android Tablets).

Comment 4

[Alex Pakhotin (:alexp)]

(In reply to donrhummy from comment #3)
> Any website.

How about these two simple test pages?
http://people.mozilla.org/~alexp/test/edit.htm
http://people.mozilla.com/~nhirata/html_tp/formsninput.html

> I'm using a Galaxy Tab 10.1

I am testing on this device right now using "English (US) Keyboard (Android keyboard)" and "Samsung keypad". Both work fine on any site I try!
What keyboard are you using?

> I'm not sure why it's happening, but it's only if I use the Tab button to go
> to the next input box. If I click in the next input box it does not occur.

Does it work when you press "Next", which takes place of Enter/Go in Samsung keyboard when editing a form, or just press Enter on the Android keyboard? These keys work as the Tab in the forms.

Something is different in your test environment compared to mine.

What version of Fennec are you using? The Build ID mentioned in the description is different from the Jan 4 nightly build, which is 20120104031035.
What exact websites do you see the problem at? (Just to make sure I'm looking at the same)
What Android and kernel version, and build number are shown in the "About device" on your Galaxy Tab? I doubt it matters though.

Comment 5

[donrhummy]

> How about these two simple test pages?
> http://people.mozilla.org/~alexp/test/edit.htm
> http://people.mozilla.com/~nhirata/html_tp/formsninput.html

Yep, it occurs there as well.
 
> I am testing on this device right now using "English (US) Keyboard (Android
> keyboard)" and "Samsung keypad". Both work fine on any site I try!
> What keyboard are you using?

"English (US) Keyboard (Android keyboard)"

> Does it work when you press "Next", which takes place of Enter/Go in Samsung
> keyboard when editing a form, or just press Enter on the Android keyboard?
> These keys work as the Tab in the forms.

I'm not sure what you mean. When I use your example sites above with the "English (US) Keyboard (Android keyboard)", there is no "next" button on the keyboard. There's a tab button and an enter button (it's the down-then-left-facing arrow that's on every enter key) but no next button. If I hit the enter key (on your example site) it simply stops key entry.

> What version of Fennec are you using? The Build ID mentioned in the
> description is different from the Jan 4 nightly build, which is
> 20120104031035.

Not sure where to find that info but it's Firefox Beta (from the Android Market) and it's the latest update.

> What Android and kernel version, and build number are shown in the "About
> device" on your Galaxy Tab? I doubt it matters though.

Android 3.2, Kernel 2.6.36.3

Comment 6

[Alex Pakhotin (:alexp)]

(In reply to donrhummy from comment #5)
> I'm not sure what you mean. When I use your example sites above with the
> "English (US) Keyboard (Android keyboard)", there is no "next" button on the
> keyboard.

The second site at http://people.mozilla.com/~nhirata/html_tp/formsninput.html contains a form, and if you use "Samsung keypad" or "Hacker's keyboard" or some other 3rd-party IME, they will turn the Enter key into "Next".

> Not sure where to find that info but it's Firefox Beta (from the Android
> Market) and it's the latest update.

This is it! Firefox Beta on Android Market is a completely different XUL-based version! Our current focus is on the Native UI version available on Aurora and Nightly channels. The UI in the latest versions was rewritten from scratch, and keyboard is now handled different way.

Thank you for the clarification. Though I still cannot reproduce the issue even with the Beta, it is clear now that we tried different versions.

Could you please download the latest nightly from here: http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android/, and check if you can see the problem in that version.

Comment 7

[donrhummy]

Why is this a priority P5? That means you will never fix this issue.

Comment 8

[donrhummy]

(In reply to Alex Pakhotin (:alexp) from comment #6)
> The second site at
> http://people.mozilla.com/~nhirata/html_tp/formsninput.html contains a form,
> and if you use "Samsung keypad" or "Hacker's keyboard" or some other
> 3rd-party IME, they will turn the Enter key into "Next".
>
> Could you please download the latest nightly from here:
> http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-
> android/, and check if you can see the problem in that version.

When I use nightly, it does not appear to occur at that site BUT it does occur at http://www.google.com/flights

Also, nightly is insanely slow with handling input.

Comment 9

[Alex Pakhotin (:alexp)]

(In reply to donrhummy from comment #7)
> Why is this a priority P5? That means you will never fix this issue.

It is supposed to be fixed in the current version, and actually I could not reproduce it even in the Beta available on Android Market.

(In reply to donrhummy from comment #8)

> When I use nightly, it does not appear to occur at that site BUT it does
> occur at http://www.google.com/flights

The input boxes on this page are not simple text edit fields, but some dynamically changed quick-search fields, which don't seem to work properly, but that is a different issue.

Where exactly do you see the issue as described in the summary?

> Also, nightly is insanely slow with handling input.

I haven't noticed that. Could you please file a separate bug, and provide more information with exact environment, URL, and steps to reproduce. There might be one already actually. Isn't it bug 713282?

Comment 10

[Adrian Tamas (:AdrianT)]

Unable to reproduce the issue described on Fennec 11 beta on the Samsung Galaxy Tab (Android 3.1). 

Please reopen the issue adding exact steps to reproduce if you can still reproduce the issue.

Comment 11

[donrhummy]

Weird. It still happens for me. I don't have the tablet with me right now, but I'll post later with the steps.

Comment 12

[donrhummy]

(In reply to adrian tamas from comment #10)
> Unable to reproduce the issue described on Fennec 11 beta on the Samsung
> Galaxy Tab (Android 3.1). 
> 
> Please reopen the issue adding exact steps to reproduce if you can still
> reproduce the issue.

It still occurs in Firefox Beta on Android.

1. Navigate to netflix.com
2. Click "Member log in" (in the upper right corner)
3. In the username, type some text (just regular alphabetical characters)
4. Hit tab

When I do this, it erases the usernam input box. If I enter an email address, it erases the "com" that's after the "myaddress@somehere.".

Comment 13

[Adrian Tamas (:AdrianT)]

I am able to reproduce this on a Samsung Galaxy Tab (Android 3.1) or Asus Transformer (Android 4.0.3) on Fennec Beta XUL 2012-04-03 if I enable always show on the "Show correction" setting. If the option is selected until a suggestion is confirmed "Tab" removes the word.

The issue is not reproducible on the Android Browser where pressing "Tab" validates the underlined word.

Comment 14

[donrhummy]

This is still occurring. Is there anything I can do to help test what's causing it?

Comment 15

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

qawanted to see if this affects native fennec

Comment 16

[donrhummy]

(In reply to Brad Lassey [:blassey] from comment #15)
> qawanted to see if this affects native fennec

Which version should I test on? Firefox? Beta? Nightly?

Comment 17

[Aaron Train [:aaronmt]]

(In reply to donrhummy from comment #16)
> (In reply to Brad Lassey [:blassey] from comment #15)
> > qawanted to see if this affects native fennec
> 
> Which version should I test on? Firefox? Beta? Nightly?

You can try out Nightly for starters at: http://nightly.mozilla.org

Comment 18

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

please renom if we get confirmation that this is an issue one trunk

Comment 19

[BMO Automation]

Closing all opened bug in a graveyard component