Closed Bug 992338 Opened 10 years ago Closed 10 years ago

[B2G][Tarako][] The first Bengali keyboard is not working correctly in the search bar


(Firefox OS Graveyard :: Gaia::Keyboard, defect)

Gonk (Firefox OS)
Not set


(blocking-b2g:1.3T+, b2g-v1.3 unaffected, b2g-v1.3T verified, b2g-v1.4 wontfix, b2g-v2.0 fixed)

blocking-b2g 1.3T+
Tracking Status
b2g-v1.3 --- unaffected
b2g-v1.3T --- verified
b2g-v1.4 --- wontfix
b2g-v2.0 --- fixed


(Reporter: demerick, Assigned: lchang)




(Whiteboard: [tarako-exploratory] eta: 4/11)


(2 files)

Attached file logcat.txt
If the user selects the first Bengali keyboard option and searches via the search bar, the search is not executed after the user taps return/enter and the string will not be saved in the search history.

The second Bengali keyboard option functions correctly - the search is executed and after exiting and returning to the search bar the string is in the history.

I have included URLs to videos of both incorrect and correct functionality.

Repro Steps:
1) Update a Tarako to BuildID: 20140403004001
2) Launch 'Settings' from the home screen
3) Tap 'Keyboards' > 'Selected keyboards' > 'Add more keyboards'
4) Tick the check box next to the first Bengali keyboard option and return to the home screen
5) Tap the 'globe' icon in the bottom left corner of the screen
6) Tap at least 3 characters and then tap enter/return in the bottom right of the virtual keyboard
7) Return home
8) Tap the the search bar

The search is never executed and does not appear in the search history

The search should be executed and the string should be saved in the history

1.3T Environmental Variables:
Device: Tarako 1.3T MOZ
BuildID: 20140403004001
Gaia: 8d212f640014db62c622e8c939ddbf8595f00438
Gecko: ddd7ba612cfe
Version: 28.1
Firmware Version: sp8810

Repro frequency: 100%
See attached: logcat.txt

Video URLS:
1st Keyboard, incorrect functionality:
2nd Keyboard, correct functionality:
This issue does not occur on the Buri 1.3 MOZ RIL

1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140401004003
Gaia: 24f562fce468fc948ac9e6185e002c23350cb9ee
Gecko: 0adf24a785f2
Version: 28.0
Firmware Version: v1.2-device.cfg

There is no option for the Bengali keyboards on the Buri device.
The videos here are covering up the bottom of the phone, so it's hard to understand when the home button is being hit. We need the videos here fixed to show the full scope of the phone.
Keywords: qawanted
QA Contact: demerick
1st Bengali Keyboard Option (Incorrect Functionality):
2nd Bengali Keyboard Option (Correct Functionality):
Looks like we have a non-functioning keyboard in the mainline build right now. We either need to fix the keyboard here or remove it from the build.
blocking-b2g: --- → 1.3T?
Component: → Gaia::Keyboard
Bengali keyboard is required. 1.3T+
ni? Luke
blocking-b2g: 1.3T? → 1.3T+
Flags: needinfo?(lchang)
I think I know how to fix it so take this bug.
Assignee: nobody → lchang
Flags: needinfo?(lchang)
Hi Steven,
We have two Bengali input methods in B2G which are "Bangla - Avro" and "Bangla - Probhat". Does Tarako need both of these two?
Flags: needinfo?(styang)
Yes, we should support both.
Flags: needinfo?(styang)
Attached file Pull Request 18020
Rudy, Could you help to review it? Thanks!
Attachment #8402548 - Flags: review?(rlu)
Comment on attachment 8402548 [details] [review]
Pull Request 18020

Looks good.


Thanks for your help.

I think we can land this, but still want to set feedback to the original author to inform him about this change.
Attachment #8402548 - Flags: review?(rlu)
Attachment #8402548 - Flags: review+
Attachment #8402548 - Flags: feedback?(aniruddha)
Whiteboard: [tarako-exploratory] → [tarako-exploratory] eta: 4/11
travis passed:

merged in gaia master:

Rudy, Thanks!
Closed: 10 years ago
Resolution: --- → FIXED
Fixed on todays 1.3T build.

1.3T Environmental Variables:
Device: Tarako 1.3T MOZ
BuildID: 20140428014001
Gaia: 8895b180ed636069473703d0e7b73086989601ce
Gecko: 7caf4b5abfce
Version: 28.1
Firmware Version: sp6821

The first Bengali keyboard works with
You need to log in before you can comment on or make changes to this bug.