+++ This bug was initially created as a clone of Bug #1022577 +++ @ Description: The uplifted patch cannot solve "Bug 1030923" on v2.0 branch. I still can reproduce it on latest v2.0 build. So, I submit a follow-up. @ STR: 1. Set homescreen as vertical version 2. Scroll screen down to button and tap home button multiple times 3. Try to click message app icon @ Demo video: https://bugzilla.mozilla.org/attachment.cgi?id=8530823 @ Expected result: Message app launch successfully @ Actural result: No response at first, and try tap screen multiple times, bring up camera app @ Build information: - Gaia-Rev f76014fd2c7528493b90d759c68ec3070233d094 - Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/53ff92e647a0 - Build-ID 20150107000201 - Version 32.0 - Device-Name flame - FW-Release 4.4.2 - FW-Incremental eng.cltbld.20150107.033038 - FW-Date Wed Jan 7 03:30:49 EST 2015 - Bootloader L1TC00011880

[Blocking Requested - why for this release]: The uplifted patch cannot solve reported bug. - https://hg.mozilla.org/releases/mozilla-aurora/rev/f78313ff6cbf The bug still can be reproduced on v2.0.

Was this fixed on 2.0 and regressed again? Or did the original fix just never fix this on 2.0?

I remember verifying bug 1022577 on aurora at the time. My bad, I didn't flip the corresponding flag and I didn't include the build details. I've just rechecked this issue today. I flashed my Flame back when the issue was present[1], I am able to reproduce the issue. Then, I flashed it on a build that included the patch[2]: I can't reproduce. Lancy, can you repro on build[2]? [1] Gaia-Rev 901646a3279c66daa7621bebb62641779d8ae22c Gecko-Rev https://hg.mozilla.org/releases/mozilla-aurora/rev/d6376896f57c Build-ID 20140609160201 Version 32.0a2 Device-Name flame FW-Release 4.3 FW-Incremental 110 FW-Date Fri Jun 27 15:57:58 CST 2014 Bootloader L1TC00011230 [2] Gaia-Rev 5b1fdc6000d35962769e789b924b24e166a27759 Gecko-Rev https://hg.mozilla.org/releases/mozilla-aurora/rev/e161f3e3b332 Build-ID 20140613160204 Version 32.0a2 Device-Name flame FW-Release 4.3 FW-Incremental 110 FW-Date Fri Jun 27 15:57:58 CST 2014 Bootloader L1TC00011230

Hi Johan, There is no June ROM on our side, so I cannot help to repro this issue using the ROM you specify.

(In reply to Lancy from comment #4) > Hi Johan, > > There is no June ROM on our side, so I cannot help to repro this issue using > the ROM you specify. Hi, Johan, My bad. We forgot to give Lancy the other base images. Sorry for any inconvenience. --- -- - --- -- - --- -- - --- -- - Hi, Lancy, Sorry. It's a JB base image with 20140613160204 build. Please access following link to download download base image and use flash tool to flash specific build. - http://cds.w5v8t3u9.hwcdn.net/v123.zip If you have further question, please feel free to let me know.

Hi, Kartikaya and Johan, Thanks for your suggestion and help. This seems to be a regression since this bug cannot be reproduced on 20140613160204 build. I would like to find the regression window. Sorry for any inconvenience. Have a nice weekend.

(In reply to William Hsu [:whsu] from comment #5) > Hi, Lancy, > > Sorry. It's a JB base image with 20140613160204 build. > Please access following link to download download base image and use flash > tool to flash specific build. > - http://cds.w5v8t3u9.hwcdn.net/v123.zip > If you have further question, please feel free to let me know. Hi, Lancy, My bad. Please skip this request.

Do you know who is going to find the regression window here? I'm assuming this regression is specific to 2.0 and the bug is still fixed on all other codelines. Please correct me if I'm wrong.

We can help with finding the regression window, but first I needed to verify the information provided at comment 3 and comment 6 were true - that this bug used to not reproduce in 2.0/Aurora branch. And I've verified myself that the information is INCORRECT. I can reproduce this bug on the build that was claimed not reproducible. Tested and issue reproduced in: Device: Flame (JB, shallow flash) BuildID: 20140613160204 Gaia: 5b1fdc6000d35962769e789b924b24e166a27759 Gecko: e161f3e3b332 Version: 32.0a2 (2.0 Aurora) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 So no, there's NOT a regression within the 2.0/Aurora branch hence a regression window is NOT possible.

Thanks for double checking Pi Wei! Was this bug harder to repro on the build you tried? Would you mind checking 2.1, 2.2 and master?

(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #10) > Thanks for double checking Pi Wei! Was this bug harder to repro on the build > you tried? Would you mind checking 2.1, 2.2 and master? On the 20140613160204 build I was able to reproduce the bug 3/3. I did check 2.1 to make sure it isn't reproducing and to see what it looks like on a build that doesn't reproduce the bug. (For regression windows we always verify that there's a clear difference between broken builds and working builds to ensure window accuracy) To complete this NI I further checked 2.2 and 3.0 master and found no contradiction to the tracking flags. (repro rate 0/6) Device: Flame 2.2 BuildID: 20150116110706 Gaia: 675c32938e51d2a8922ed1ecc22d1ef05da6536b Gecko: 4ac73262c07e Version: 37.0a2 (2.2) Firmware: V18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 (repro rate 0/8) Device: Flame 3.0 Master BuildID: 20150116060902 Gaia: 5ae81fcc0d8568a50d0bf8491004bc9485b3a9ae Gecko: 5438e3f74848 Version: 38.0a1 (3.0 Master) Firmware: V18D-1 User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

(In reply to Pi Wei Cheng [:piwei] from comment #9) > We can help with finding the regression window, but first I needed to verify > the information provided at comment 3 and comment 6 were true - that this > bug used to not reproduce in 2.0/Aurora branch. And I've verified myself > that the information is INCORRECT. I can reproduce this bug on the build > that was claimed not reproducible. > > Tested and issue reproduced in: > Device: Flame (JB, shallow flash) > BuildID: 20140613160204 > Gaia: 5b1fdc6000d35962769e789b924b24e166a27759 > Gecko: e161f3e3b332 > Version: 32.0a2 (2.0 Aurora) > Firmware: V123 > User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 > > So no, there's NOT a regression within the 2.0/Aurora branch hence a > regression window is NOT possible. Hi, Pi Wei, Thanks for your help! :)

[Triage] 1. per above comments it seems a regression from 1.4, but not a regression for 2.0 itself. 2. per video it doesn't looks like normal user behavior. (need fast scroll up/down homescreen) 3. also considering 2.0 timing and no partner ask for this. So de-tag for 2.0 now.

Since this bug is restricted to an old codeline and people don't seem to be running into it, I'm going to close this bug as not worth the effort to fix. Feel free to reopen if this changes.

Hi, Lancy, Could you help confirm this bug on latest v2.0m?

Hi William, This issue exist in woodduck 2.0m latest build. Occurrence time:04:17. Occurrence rate:10/10 See the attachments:Verify1_1119177_logcat_woodduck.txt and Verify1_1119177_video_woodduck.MP4. STR: 1. Set homescreen as vertical version 2. Scroll screen down to button and tap home button multiple times 3. Try to click message app icon Expected result: Message app launch successfully. Actural result: bring up marketplace app. Woodduck build: Gaia-Rev bdf3742fbbb900fd940fbbd6c8f7b1ae09521874 Gecko-Rev 5100d57325f1ea992f2d6aa086829c27f5056102 Build-ID 20150202050313 Version 32.0 Device-Name jrdhz72_w_ff FW-Release 4.4.2 FW-Incremental 1422824710 FW-Date Mon Feb 2 05:05:29 CST 2015

(In reply to Lancy from comment #16) > Created attachment 8557820 [details] > Verify1_1119177_logcat_woodduck.txt > > Hi William, > > This issue exist in woodduck 2.0m latest build. > Occurrence time:04:17. > Occurrence rate:10/10 > See the attachments:Verify1_1119177_logcat_woodduck.txt and > Verify1_1119177_video_woodduck.MP4. > > STR: > 1. Set homescreen as vertical version > 2. Scroll screen down to button and tap home button multiple times > 3. Try to click message app icon > > Expected result: > Message app launch successfully. > > Actural result: > bring up marketplace app. > Hi, Lancy, Good job! Thanks for your prompt help. :)

Bad user experience. Nominate this bug since it is easy to reproduce on the next shipping device. Add tag - "2.0m?" Please minus this bug if pals don't think this is a high priority issue. Many thanks.