806106 - Field not accepting input

Status: RESOLVED WORKSFORME

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

Description

[Alex]

Attachment: Screenshot_2012-10-27-21-14-04.png

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121010144125

Steps to reproduce:

Tried to enter the information into the search engine, but the cursor does not respond and the data on the screen did not appear. [Android 4.0.4, device - samsung galaxy tab 2]


Actual results:

Unable to enter the data (only pasting from the clipboard) or delete \ change them. Just no response to keystrokes. It does not matter - a mobile version or not, the data is still not entered. In the Google search box, the search bar add-ons and other windows for data entry	etc.


Expected results:

In the window for data entry had something to appear.:)

Comment 1

[Aaron Train [:aaronmt]]

Which version of Firefox and which input method (Android keyboard) is that (and which version is it?)

Comment 2

[Alex]

(In reply to Aaron Train [:aaronmt] from comment #1)
> Which version of Firefox and which input method (Android keyboard) is that
> (and which version is it?)

Firefox Beta 17.0. Error occurs when you use a Samsung system keyboard(handwriting) and Smart Keyboard PRO v4.6.3

Comment 3

[Demetrius S.]

I've had something like this bug occur recently on nightly while typing in Reddit. The only way to ge the text to show up is usually to lower the keyboard, which will then show the text.

Comment 4

[Aaron Train [:aaronmt]]

QA Triage Comment

Jim, can you access this bug for priority as it's reproducible on Beta.

Comment 5

[Aaron Train [:aaronmt]]

I'm not able to reproduce this with the Samsung Galaxy Tab 2.0" and Smart Keyboard Pro. I tried en-US and even русские, and was not able to reproduce. When I type any character on the Google Search, I get search results on a new page immediately. I also tried with the stock default Samsung keyboard and found no issues.

This is WFM.

Comment 6

[Alex]

(In reply to Aaron Train [:aaronmt] from comment #5)
> I'm not able to reproduce this with the Samsung Galaxy Tab 2.0" and Smart
> Keyboard Pro. I tried en-US and even русские, and was not able to reproduce.
> When I type any character on the Google Search, I get search results on a
> new page immediately. I also tried with the stock default Samsung keyboard
> and found no issues.
> 
> This is WFM.

The error persists through time. Here's the recorded logs to reproduce the problem.
http://www.mediafire.com/?7brhl3wopojwl7l

Comment 7

[(inactive) Jim Chen [:jchen] [:darchons]]

(In reply to Alex from comment #6)
> 
> The error persists through time. Here's the recorded logs to reproduce the
> problem.
> http://www.mediafire.com/?7brhl3wopojwl7l

Thank you Alex! Can you try using this build and see if it works? http://people.mozilla.org/~nchen/fennec-19.0a1-ime-rework.apk

Comment 8

[Alex]

(In reply to Jim Chen [:jchen :nchen] from comment #7)

> Thank you Alex! Can you try using this build and see if it works?
> http://people.mozilla.org/~nchen/fennec-19.0a1-ime-rework.apk

I opened the search page to check addons [https://addons.mozilla.org/en-US/android/] - everything worked. Worth it to switch to Google - the error appears again. On the search page addons also gave input information.

new log (suddenly be helpful)
http://www.mediafire.com/view/?53hrtj0h6pe9dfj

Comment 9

[(inactive) Jim Chen [:jchen] [:darchons]]

(In reply to Alex from comment #8)
> (In reply to Jim Chen [:jchen :nchen] from comment #7)
> 
> > Thank you Alex! Can you try using this build and see if it works?
> > http://people.mozilla.org/~nchen/fennec-19.0a1-ime-rework.apk
> 
> I opened the search page to check addons
> [https://addons.mozilla.org/en-US/android/] - everything worked. Worth it to
> switch to Google - the error appears again. On the search page addons also
> gave input information.
> 
> new log (suddenly be helpful)
> http://www.mediafire.com/view/?53hrtj0h6pe9dfj

I don't see anything useful... It seems like the keyboard is not communicating with Fennec at all. Can you uninstall and reinstall the keyboard and try again?

Also, when everything works, can you run 'adb logcat -c', use the keyboard, and then run 'adb logcat' to get the log for only when the keyboard works.

Then, when the bug appears, can you do the same steps again to get the log for only when the keyboard is not working.

This way I can compare the two logs and see what is the difference. Thanks!

Comment 10

[Alex]

Thank you for your attention to this problem.)
After reinstalling:
http://www.mediafire.com/?2e9j5i4va8iez8i

Comment 11

[(inactive) Jim Chen [:jchen] [:darchons]]

(In reply to Alex from comment #10)
> Thank you for your attention to this problem.)
> After reinstalling:
> http://www.mediafire.com/?2e9j5i4va8iez8i

Sorry Alex, I still cannot reproduce the bug, and I don't see any clues in the log files. Maybe see if you can try different keyboards? And maybe another app that you installed is interfering with the keyboard?

Comment 12

[Alex]

(In reply to Jim Chen [:jchen :nchen] from comment #11)
> (In reply to Alex from comment #10)
> > Thank you for your attention to this problem.)
> > After reinstalling:
> > http://www.mediafire.com/?2e9j5i4va8iez8i
> 
> Sorry Alex, I still cannot reproduce the bug, and I don't see any clues in
> the log files. Maybe see if you can try different keyboards? And maybe
> another app that you installed is interfering with the keyboard?

I do not know the standard keyboard also fails to enter, one has only to refresh the page or go to another((. I can record video from the screen, as it happens.

Comment 13

[Popolon]

I‘ve the same problem on the Samsung Galaxy Note 10.1 (near the same than the Tab 2, but with wacom S-Pen and some pressure sensitive application).

After removing all my input methods (keyboards), including Sogou pinyin (pinyin/handwritting chinese) from here :
http://pinyin.sogou.com/

And adding nightly (19a), I understand a reproductible way to reproduce the bug in my case and remove it. In every cases URL bar works perfectly, only html text inputs are impacted by the bug.

* If I launch for the first time firefox (16 or 19), I can fill a form without problems.
* If I browse a little the bug appear
* If I quit (by menu =>quit) Firefox and launch it again, the bug disappear.

* If I click on home button (and then iconify firefox) and click again on firefox icon the bug reappear.
* If I quit (again) by quit menu and launch again firefox, I can fill at least one form, sometime several (at least in 19).

ff 16 seems to be far less stable sometime everything slowdown and there is precision bug (if I click on find in wikipedia, it click on login/register).
If 16 become unusable (slowdown everything), I can get again handle on device by clicking on Home button, then kill it in task  manager (accessible with the little ^ in the middle of android 4.0 on tablet. After killing it, If I relaunch firefox (16 or 19) the keyboard bug continue. If I then quit by menu (on 19 at least), and restart firefox, everything works well again.

So my temporary conclusion is that the bug can be (temporary) eliminated every time firefox is quitted using quit in menu. The bug is persistant over sessions (crash, iconification, kill). Could the blocking situation be keeped to cache files or configuration files or something like that ???

Comment 14

[Popolon]

I cleared every application data (using parameters => application manager).

I don't have any more slowdown since but the bug continue on both version

I've reinstalled sogou pinyin input method, bug occur the same way, so I think this method doesn't have influence on the bug.