1166193 - [Rocketbar][512MB flame] Unable to scroll Rocketbar search results with keyboard invoked

Status: RESOLVED WORKSFORME

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

Description

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

[Blocking Requested - why for this release]: regression

STR:

1. Flash the phone with lastet m-c (f65cc0022a0e)
2. Reboot the phone
3. Unlock and tap rocket bar
4. Search something
5. Attempt to scroll the search result

Expected:

1. I should be able to scroll the search results.

Actual:

1. Sometimes it works, sometimes it doesn't and another reboot will fix it.

Note:

I only flash Gecko to the latest m-c and saw this. I don't know if QA can reproduce this with different way of flashing.

Comment 1

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

I was unable to reproduce this issue on the latest central build.  Leaving the tag for someone else to try.

Environmental Variables:
Device: Flame 3.0
BuildID: 20150519030124
Gaia: 97dc139f1a690224e98533a86526c4165eed1db5
Gecko: 4fb7ff694bf5
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Comment 2

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

We need to confirm the steps first before tagging other things.

Comment 3

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

What I'm seeing is if I have keyboard on the screen, I can't scroll the rocketboar results. Is this what you were seeing?

STR:
1) Tap on Rocketbar
2) Type a word on Rocketbar, and observe search results display on screen
3) With keyboard still on screen, try to scroll the search result on upper half of screen

Observe the results are unable to be scrolled. User can dismiss the keyboard by long tapping on space key, and it becomes scrollable again. This is 100% reproducible.

Comment 4

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

Comment 3 was tested on:
Device: Flame 3.0 (KK, full flashed, 319MB)
BuildID: 20150519010201
Gaia: 762cbd16712484f93f485e89f5363686540a3db7
Gecko: f65cc0022a0e
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Comment 5

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

(In reply to Pi Wei Cheng [:piwei] from comment #3)
> What I'm seeing is if I have keyboard on the screen, I can't scroll the
> rocketboar results. Is this what you were seeing?
> 
> STR:
> 1) Tap on Rocketbar
> 2) Type a word on Rocketbar, and observe search results display on screen
> 3) With keyboard still on screen, try to scroll the search result on upper
> half of screen
> 
> Observe the results are unable to be scrolled. User can dismiss the keyboard
> by long tapping on space key, and it becomes scrollable again. This is 100%
> reproducible.

Yes that's what I am seeing. Thank you.

Comment 6

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

You're welcome. Changing title to better describe this bug. This issue occurs on Flame 3.0.

Device: Flame 3.0
BuildID: 20150520010202
Gaia: 600fd8249960b8256af9de67d9171025bb9a3ff3
Gecko: ac277e615f8f
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

---

This issue does NOT occur on Flame 2.2. Keyboard dismisses once user starts to scroll on search results.

Device: Flame
BuildID: 20150520002502
Gaia: 63e9eeec3032318f8a240f80b6a184fa4b50b6e1
Gecko: a89755309dea
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

----

I'm working on getting the regression window.

Comment 7

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

My mistake. I thought I was on 319MB of Flame, but turns out I've been on 512MB since yesterday. I've confirmed that this issue does NOT happen on 319MB. There seems to be other discrepancies that I need to figure out in order to find the window. I've also confirmed 2.2 is unaffected with 512MB.

Comment 8

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

After further investigation I found that this issue is no longer reproducing on the latest tinderbox central build. Nightlies get spawn later so it's highly likely that this issue will not reproduce on tomorrow's nightly.

On central tinderbox eng I was able to reproduce the bug on the following build:
Device: Flame (KK, shallow flashed, 512MB)
BuildID: 20150518172622
Gaia: 762cbd16712484f93f485e89f5363686540a3db7
Gecko: f65cc0022a0e
Version: 41.0a1 (3.0 Master) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

On central tinderbox eng I was NOT able to reproduce the bug on the following build:
Device: Flame (KK, shallow flashed, 512MB)
BuildID: 20150520065444
Gaia: b290c77ccb7ab0af599b3d8287b71b9970d8dcb0
Gecko: 8d8df22fe72d
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 41.0a1 (3.0 Master) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

---

NI reporter to test on latest, or I can test on next nightly to confirm that it is fixed and then we can close this bug out.

Comment 9

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

Let's close this out first. I don't pull latest code daily.