[Aries][Keyboard] Keyboard does not reappear after receiving and ending a call, but text field still has focus.

NEW
Unassigned

Status

Firefox OS
Gaia::Keyboard
2 years ago
2 years ago

People

(Reporter: Marty, Unassigned)

Tracking

(Blocks: 1 bug)

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-master affected)

Details

(Whiteboard: [2.5-Daily-Testing][Spark], URL)

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8636285 [details]
logcat-keyboard.txt

Description:
If the user has the keyboard open at a text field when they receive a call, once the call is ended, the text field will still appear active, with a blinking cursor, but the keyboard will not reappear until the user taps away from and back to the text field.

This seems to occur in most text fields, including in Messages, Contacts, and Email.

Repro Steps:
1) Update a Aries to 20150720101908
2) Messages and begin composing an SMS so that the keyboard is open
3) Call the DUT from another device, then end the call

Actual:
The text field is still active, but the keyboard does not open.

Expected:
The text field is active and the keyboard reopens.

Environmental Variables:
Device: Aries 2.5
Build ID: 20150720101908
Gaia: a47e0c58dd1340a17be7cc96ccd90fcad15a922b
Gecko: 5df788c56ae7
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Repro frequency: 9/10
See attached: logcat, video (URL)
(Reporter)

Comment 1

2 years ago
This issue does NOT occur on Flame 2.5 builds.
The text field is active and the keyboard reopens.

Environmental Variables:
Device: Flame 2.5
Build ID: 20150720010206
Gaia: 3fac3ed7b8c887351098ffc677769ddc36abb3d0
Gecko: 202e9233d130
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Not going to nominate to block release but is a papercut for user experience
Blocks: 1171119
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
You need to log in before you can comment on or make changes to this bug.