Closed Bug 755599 Opened 12 years ago Closed 12 years ago

Typing after "Select All" text or using Firefox textfield history inserts at wrong position when using a predictive text VKB

Categories

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

ARM
Android
defect
Not set
normal

Tracking

(firefox14 fixed, firefox15 verified, blocking-fennec1.0 +)

RESOLVED DUPLICATE of bug 688438
Tracking Status
firefox14 --- fixed
firefox15 --- verified
blocking-fennec1.0 --- +

People

(Reporter: cpeterson, Assigned: cpeterson)

References

()

Details

(Keywords: inputmethod, Whiteboard: VKB)

STR:
1. Using the Galaxy Nexus's stock VKB (with spelling suggestions) or Swype VKB on any device, go to a page with a text field (like the Firefox Support web page)
2. Focus the text field and select a suggestion from Firefox's list your text form history
3. Type a character

ER:
The character should be appended to the autocompleted text.

AR:
The character is inserted at the beginning of the autocompleted text.


4. Then "Select All" text in the text field
5. Type a character

ER:
The character should overwrite the selected text.

AR:
The character may be inserted at the beginning or middle of the selected text. The composition string also goes haywire.
This bug should probably block 1.0 because Galaxy Nexus's stock VKB is affected.
Assignee: nobody → cpeterson
blocking-fennec1.0: --- → ?
blocking-fennec1.0: ? → +
blocking-fennec1.0: + → ?
Keywords: inputmethod
blocking-fennec1.0: ? → +
QA - can we get tests for other devices?
Keywords: qawanted
I think the problem is more related to different IMEs than different devices.

I think this bug was triggered by an Fx15 regression from Ehsan's fix for bug 612128. Fortunately, Ehsan has a regression fix in bug 688438, but there is additional Android work required.
I relanded the fix to bug 688438 on the inbound branch.  Please let me know if I can help more.
Ehsan's fix for bug 688438 fixes this bug on Nightly 15 (2012-05-26). This was a regression, so Aurora 14 was not affected.

https://hg.mozilla.org/mozilla-central/rev/4651104e0d0e
No longer blocks: 612128
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I am unable to reproduce the issue using either predictive or Swype keyboards on Samsung Galaxy S2 (Android 2.3.4) or on the HTC Desire (Android 2.2) on Nightly 15.0a1 2012-05-27.
Keywords: qawanted
I cannot reproduce the bug using either Android or Swype keyboards

Nightly 15.0a1 (2012-05-29)
Samsung Galaxy SII (2.3.4)

Gabriela, if you see this again, please reopen.
Status: RESOLVED → VERIFIED
(In reply to Catalin Suciu from comment #8)
> I cannot reproduce the bug using either Android or Swype keyboards
> 
> Nightly 15.0a1 (2012-05-29)
> Samsung Galaxy SII (2.3.4)
> 
> Gabriela, if you see this again, please reopen.

I'm sorry but I'm still seeing the bug in Nightly 15.0a1 (2012-05-30), only in landscape mode though, using Galaxy S2 and Android 2.3.4 too, that's why I'm reopening the bug.

What I see is the following:
The cursor sort of switches back an forth. I mean I can see my password's first character for a few seconds as usual. Then I type the second one, I cannot see the typed character at all and the cursor blinks at the left of the first character I typed. The same happens with all the characters I type after the first one and when I tap login I get a message about my password not being correct. 
Please try and see if you get the same. If not, I'll try to take some screenshots. I know a screencast would be best but I've tried before for another bug, regretfully the file was too big to upload here or its format was not supported.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
hi, Gabriela:

1. I can reproduce the "jumping cursor" with the Galaxy S2's landscape keyboard. I believe that bug is unrelated, so I opened a new bug report to  track that problem: bug 759857

2. I was not able to reproduce the password problem. I created a Windows Live ID account and I was able to successfully log into login.live.com. Since the jumping cursor did not affect the correct text input of the username, I don't think it would affect the password either.

* Can you log into login.live.com using the portrait mode keyboard? The Galaxy S2's landscape mode keyboard is special because it uses the full screen.
Hi Chris:

 1. I've seen bug 759857. It's not the same as what I see though because in my case the entered text is not correct, that is: I cannot sign in because the password in incorrect due to the switching cursor back to forth.

 * Using the portrait mode keyboard I can login without any issues.





> 
> 2. I was not able to reproduce the password problem. I created a Windows
> Live ID account and I was able to successfully log into login.live.com.
> Since the jumping cursor did not affect the correct text input of the
> username, I don't think it would affect the password either.
> 
> * Can you log into login.live.com using the portrait mode keyboard? The
> Galaxy S2's landscape mode keyboard is special because it uses the full
> screen.
(In reply to Gabriela from comment #11)
>  1. I've seen bug 759857. It's not the same as what I see though because in
> my case the entered text is not correct, that is: I cannot sign in because
> the password in incorrect due to the switching cursor back to forth.
> 
>  * Using the portrait mode keyboard I can login without any issues.

I'm not sure why the jumping cursor would cause problems for password text input, but not regular text input. I am able to successfully login with both landscape and portrait keyboards on my Galaxy S2.

To test whether the jumping cursor is a problem, try entering your password in a text field where you can see the characters (such as the address bar) and then select/cut/paste your password text into the password box's landscape keyboard. Pasting your password should "inject" your password as whole text. This should workaround any issues with individual letters being rearranged by the jumping cursor. I verified that this procedure worked for me.
The above workaround works for me too, but it doesn't solve the issue. So I think the jumping cursor is the problem because it changes the password's character's order.
Gabriela, this sounds like a new issue. I'm going to re-close this as fixed. Can you please file a new bug to track what you're seeing?
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Resolution: FIXED → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.