1019360 - [v1.4] Keyboard will not work if do as follow before keyboard shows completely

Status: RESOLVED FIXED

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

Description

[Wei Gao (Spreadtrum)]

OS version
---------------------------------------------
FireFoxOS v1.4

Reproduce steps:
---------------------------------------------
1、When the keyboard appears from bottom of screen with sliding effects, press "L" button before the keyboard shows completely and keep the press.
2、After keyboard shows completely, quick release and then quickly click "L" again.
3、The keyboard will hide, then alternative char shows is unnormal and keyboard will not work unless restart the ffos system.

Actual result:
---------------------------------------------
Keyboard will not work unless restart the ffos system.

Expected result:
---------------------------------------------
work normal

Comment 1

[Wei Gao (Spreadtrum)]

Attachment: VID_0001.3gp

This is the video of my operation to reproduce it.

Please help to check it.

Comment 2

[Wei Gao (Spreadtrum)]

Hi Evelyn

Please help to check this bug.

Thanks

Comment 3

[Jason Smith [:jsmith]]

Probably a regression. QA Wanted to check 1.3.

Comment 4

[Evelyn Hung]

I can't follow the STR, how can you press the 'L' button in the very short time period? even I pressed before keyboard loaded, I still can't reproduce the issue. :(

Comment 5

[Pi Wei Cheng [:piwei] (inactive)]

Issue is NOT reproducible following the STR on Flame base image v10g-2 (1.3).

I can't actually repro this on today's 1.4 Flame either.
> 3、The keyboard will hide, then alternative char shows is unnormal and keyboard will not work unless restart the ffos system.

After the keyboard hides, when tapping to invoke it again, it types normally as expected.

Comment 6

[Preeti Raghunath(:Preeti)]

Can't repro now, please provide updates STRs and nom when we can repro

Comment 7

[Shufang.Xu]

(In reply to Preeti Raghunath(:Preeti) from comment #6)
> Can't repro now, please provide updates STRs and nom when we can repro

1. Use the finger of the left hand click, let the sliding keyboard appear.

2. when the keyboard appear, the finger of the right hand quickly long press "L".Note:Almost in the presence of the keyboard, hold "L" button nearly at the same time.

3.After keyboard shows completely, quick release and then quickly click "L" again.

4.The keyboard will hide, then alternative char shows is unnormal and keyboard will not work unless restart the ffos system.

Comment 8

[Shufang.Xu]

(In reply to Preeti Raghunath(:Preeti) from comment #6)
> Can't repro now, please provide updates STRs and nom when we can repro

(In reply to Pi Wei Cheng [:piwei] from comment #5)
> Issue is NOT reproducible following the STR on Flame base image v10g-2 (1.3).
> 
> I can't actually repro this on today's 1.4 Flame either.
> > 3、The keyboard will hide, then alternative char shows is unnormal and keyboard will not work unless restart the ffos system.
> 
> After the keyboard hides, when tapping to invoke it again, it types normally
> as expected.


1. Use the finger of the left hand click, let the sliding keyboard appear.

2. when the keyboard appear, the finger of the right hand quickly long press "L".Note:Almost in the presence of the keyboard, hold "L" button nearly at the same time.

3.After keyboard shows completely, quick release and then quickly click "L" again.

4.The keyboard will hide, then alternative char shows is unnormal and keyboard will not work unless restart the ffos system.

Comment 9

[Shufang.Xu]

ALCATEL contrast machine, and comparison of flamev1.4 machine also has this problem.
please help check it,Thank you very much !

Repro Test:
 
1. Use the finger of the left hand click, let the sliding keyboard appear.

2. when the keyboard appear, the finger of the right hand quickly long press "L".Note:Almost in the presence of the keyboard, hold "L" button nearly at the same time.

3.After keyboard shows completely, quick release and then quickly click "L" again.

4.The keyboard will hide, then alternative char shows is unnormal and keyboard will not work unless restart the ffos system.

Comment 10

[Shufang.Xu]

(In reply to Shufang.Xu from comment #8)
> (In reply to Preeti Raghunath(:Preeti) from comment #6)
> > Can't repro now, please provide updates STRs and nom when we can repro
> 
> (In reply to Pi Wei Cheng [:piwei] from comment #5)
> > Issue is NOT reproducible following the STR on Flame base image v10g-2 (1.3).
> > 
> > I can't actually repro this on today's 1.4 Flame either.
> > > 3、The keyboard will hide, then alternative char shows is unnormal and keyboard will not work unless restart the ffos system.
> > 
> > After the keyboard hides, when tapping to invoke it again, it types normally
> > as expected.
> 
> 
1. Use the finger of the left hand click, let the sliding keyboard appear.

2. when the keyboard appear, the finger of the right hand quickly long press
"L".Note:Almost in the presence of the keyboard, hold "L" button nearly at
 the same time.
 
3.After keyboard shows completely, quick release and then quickly click "L"
 again.

4.The keyboard will hide, then alternative char shows is unnormal. Click again, the keyboard back to normal

Comment 11

[Shufang.Xu]

(In reply to Preeti Raghunath(:Preeti) from comment #6)
> Can't repro now, please provide updates STRs and nom when we can repro

1. Use the finger of the left hand click, let the sliding keyboard appear.

2. when the keyboard appear, the finger of the right hand quickly long press
"L".Note:Almost in the presence of the keyboard, hold "L" button nearly at
 the same time.
 
3.After keyboard shows completely, quick release and then quickly click "L"
 again.

4.The keyboard will hide, then alternative char shows is unnormal. Click again, the keyboard back to normal

Comment 12

[Shufang.Xu]

I have two ideas:
1) make the keyboard display faster.
2) before the keyboard fully displayed, click on the screen is invalid
This may be solved the problem,

Comment 13

[Evelyn Hung]

[Blocking Requested - why for this release]: it seems could be reproduced again per comment 9. 
also qawanted for a try.

Comment 14

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

This issue does occur on 1.4 Flame, 1.4 Buri, and 1.3 Buri

The keyboard dismisses and then becomes unresponsive and the device must be restarted to use it again.

Environmental Variables:
Device: Flame 1.4
BuildID: 20140801103150
Gaia: 8b476ef4cca719a2e90eb30fdcef0c3617cf574b
Gecko: 641db5b6540c
Version: 30.0 (1.4) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Environmental Variables:
Device: Buri 1.4
BuildID: 20140804021228
Gaia: 9377274b17200a60cebcd2427d489a7756c4cc72
Gecko: d3169b0707ea
Version: 30.0 (1.4) 
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0


Environmental Variables:
Device: Buri 1.3
BuildID: 20140721151227
Gaia: 23f55be856cef53c6604a6fe4aeb09061afbc897
Gecko: 9727017eabb9
Version: 28.0 (1.3) 
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0



This issue did not occur on 2.0 Flame and 2.1 Flame.

The keyboard remains responsive even when reproducing this issue.  However the keyboard will dismiss itself as in 1.4 and 1.3

Environmental Variables:
Device: Flame 2.0
BuildID: 20140804060132
Gaia: 4ab7384db7aee130be165a699472cc19405a4456
Gecko: 5e94ab16ec71
Version: 32.0 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Flame Master
BuildID: 20140804041427
Gaia: af9a0a24fb9f4c5ced3602bc14053bd49b136344
Gecko: 71497ed2e0db
Version: 34.0a1 (Master) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 15

[Shufang.Xu]

(In reply to Evelyn Hung [:evelyn] from comment #13)
> [Blocking Requested - why for this release]: it seems could be reproduced
> again per comment 9. 
> also qawanted for a try.

According to comment14, the problem is real exist, Could you tell me who can help to solve this problem, thank you very much again !

Comment 16

[Evelyn Hung]

Hi Rudy, 
could you help to investigate this issue while Luke's taking sick leaves? Thank you.

Comment 17

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

I'll try to reproduce this on Flame v1.4 and investigate the root cause.

Comment 18

[Shufang.Xu]

(In reply to Rudy Lu [:rudyl] from comment #17)
> I'll try to reproduce this on Flame v1.4 and investigate the root cause.

Thank you very much !

Comment 19

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

Attachment: Patch V1, for v1.4

[Root cause]
The root cause is similar to what I stated in bug 1013739 comment 19,
--
We could not receive the touchend event after pressing 'L' and releasing it again, so we did not reset the state that alternative menu is showed, and in this state, we would ignore all new touch events.
--

And in hideKeyboard(), we would do early return if the keyboard is not rendered completely, in this early turn, we did not do clearTouchedKeys() to reset the state.

This issue would not occur on v2.0 even when I run keyboard as in-process.
So, I'll create a v1.4 specific patch for this.

Tim, could you help review this patch?

Comment 20

[Wayne Chang [:wchang]]

Unrecoverable until reboot, considerable user impact and from video it does seem like a possible problem.

Comment 21

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Comment on attachment 8467602 [details] [review]
Patch V1, for v1.4

Let's ask QA to double verify if the same STR does not reproduce on 2.0/2.1.

Please try it on normal Flame and 319MB Flame on both branches (that's four config to check).

Comment 22

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Sorry, I already see repro info on comment 14. So I guess what's needed now is just Flame 319MB on both 2.0/2.1 branch.

Comment 23

[Rudy Lu [:rudyl] (inactive after 2015/7/3)]

Landed to Gaia v1.4 branch,
https://github.com/mozilla-b2g/gaia/commit/6bbf43f22812a3c53225f62960fa7e9be4d45f6b

Comment 24

[Duane Dixon [:ddixon]]

Attempted to reproduce issue with 319 MB memory. 

I used the STR listed in comment 9.  

Issue DOES NOT occur in 2.0, and 2.1 Flame builds. 

Device: Flame Master
Build ID: 20140806090025
Gaia: 5e6ef81cb9e917657ce050f598229dfc83c58b8f
Gecko: f41a267983c1
Version: 34.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Device: Flame 2.0
Build ID: 20140806084615
Gaia: 47fa0ba8197e71cc7034943ff037642e7f35cdfe
Gecko: 4feed2803746
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 25

[[:SalvadorR]]

This will need a new test case for it to be covered

Comment 26

[KTucker [:KTucker][Inactive 3/4/2016]]

Test case added in moztrap:

https://moztrap.mozilla.org/manage/case/14375/