Closed Bug 810388 Opened 12 years ago Closed 12 years ago

Galaxy S II landscape mode's extracted text editor displays characters in random order

Categories

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

17 Branch
ARM
Android
defect
Not set
normal

Tracking

(firefox18 wontfix, firefox19 fixed)

VERIFIED FIXED
Firefox 19
Tracking Status
firefox18 --- wontfix
firefox19 --- fixed

People

(Reporter: cpeterson, Unassigned)

References

()

Details

Attachments

(1 file)

This affects Aurora 18, but not Nightly 19.

STR:
1. On a Galaxy S II, load my favorite IME test page in Aurora 18: http://support.mozilla.org/
2. Rotate phone to landscape orientation
3. Tap input focus in the Help page's text input
4. Start typing

RESULT:
The extracted text editor displays that characters in a seemingly random order.

Please see the attached screenshot where I attempt to type "hello world".
This occurs on release 17 & beta 18 as well. Appears to be in reverse order (both in display & when submitted to web pages like Google search), maybe the test case above was affected by predictive text?
I can repro on Release 17 and Beta 18, but only when enabling the default Samsung keyboard's XT9 predictive text. The good news is that I can NOT repro on Aurora 19 or Nightly 21 with XT9 predictive text enabled or disabled. But I see now that was what I reported when I filed this bug two months ago. <:)

jchen, which channel is your big IME rewrite in? Or do you know of a different fix in 19 that could be uplifted to 18?

Beta is currently 18, but will be uplifted to 19 (which has the fix) sometime in the next few days. So even if we identified the fix, we would probably not risk uplifting it to Release 18.
Version: unspecified → Firefox 17
Big IME rewrite is 19.
(In reply to Chris Peterson (:cpeterson) from comment #2)
> I can repro on Release 17 and Beta 18, but only when enabling the default
> Samsung keyboard's XT9 predictive text. The good news is that I can NOT
> repro on Aurora 19 or Nightly 21 with XT9 predictive text enabled or
> disabled. But I see now that was what I reported when I filed this bug two
> months ago. <:)
> 
> jchen, which channel is your big IME rewrite in? Or do you know of a
> different fix in 19 that could be uplifted to 18?
> 
> Beta is currently 18, but will be uplifted to 19 (which has the fix)
> sometime in the next few days. So even if we identified the fix, we would
> probably not risk uplifting it to Release 18.

I think it's related to threading/race conditions that the rewrite fixed. And I agree it's not worth the risk to have a fix on Release at this point.
I'm resolving this bug as fixed in 19.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 19
Verified fixed on:
-build: Firefox for Android 19, 20.0b1 build 3 (2013-02-22), 21.0a2 (2013-02-25),  22.0a1 (2013-02-25)
-device: Samsung Galaxy S II
-OS: Android 4.0.3
Status: RESOLVED → VERIFIED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: