Closed Bug 1100496 Opened 10 years ago Closed 10 years ago

[SMS] Tapping the to portion of the message causes the keyboard to flicker on and off

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.0 unaffected, b2g-v2.1 affected, b2g-v2.2 unaffected)

RESOLVED DUPLICATE of bug 1057898
tracking-b2g backlog
Tracking Status
b2g-v2.0 --- unaffected
b2g-v2.1 --- affected
b2g-v2.2 --- unaffected

People

(Reporter: rmitchell, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [2.1-exploratory-3])

Attachments

(1 file)

Description:
When user is tapping the to portion of the message causes the keyboard to flicker on and off


Repro Steps:
1) Update a Flame to 20141117001201
2) Go to messenger 
3) Tap a message thread or start a new one
4) Tap the to portion of the message 


Actual:
Keyboard flickers on and off 


Expected:
Keyboard is uneffected 

Environmental Variables:
Device: Flame 2.1
Build ID: 20141117001201
Gaia: 81160ad79e5b4c21967418dd63f1a1d08d77924e
Gecko: 3572aa3e6766
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


Repro frequency:100%
See attached:logcat video clip: https://www.youtube.com/watch?v=LccdqVrWd98&list=UUlBL08Rzw8WLqi9VvigAvBw
Flags: needinfo?(dharris)
This issue DOES NOT  occur on  2.2 (319mb)(Kitkat Base)(Shallow Flash) 2.0 (319mb)(Kitkat Base)(Shallow Flash) 
flickering does not occur 
Flame 2.2

Environmental Variables:
Device: Flame 2.2
Build ID: 20141117040203
Gaia: ddf5b92f43ec27c93ad4fea4fd1207da8936b8e7
Gecko: 21b745197618
Version: 36.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0


Flame 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141117000200
Gaia: 086a668942292168f312b3bb53e275fa0886fab1
Gecko: a57b299c5cf2
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
[Blocking Requested - why for this release]:

I think that's because we blur+focus here.

Hey Rudy, do you think this could be handled in Keyboard, since the issue seems to exist in v2.1 only?

Asking for a blocking status; but if it's not a blocker then we probably don't need to spend time on it.
blocking-b2g: --- → 2.1?
Flags: needinfo?(rlu)
Blocking decision was made in comment 2.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
triage: not blocking because tapping on the "to" is not a usual case. also, this defect is not breaking functionality.
blocking-b2g: 2.1? → backlog
FWIW, on v2.1 the keyboard manager would receive a blur and then a focus event.
While on master (v2.2) it would only receive a focus event when tapping on "to".

As this issue would not occur on current master, guess we could close this as wontfix.
Thanks.
Flags: needinfo?(rlu)
I think this issue has addressed by bug 1057898, so dupe to that.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: