Closed
Bug 1233926
Opened 9 years ago
Closed 9 years ago
Unable to search on web while selecting time on new calendar event
Categories
(Firefox OS Graveyard :: Gaia::System::Input Mgmt, defect)
Tracking
(b2g-v2.5 unaffected, b2g-master verified)
VERIFIED
DUPLICATE
of bug 1224128
Tracking | Status | |
---|---|---|
b2g-v2.5 | --- | unaffected |
b2g-master | --- | verified |
People
(Reporter: feer56, Assigned: timdream)
References
Details
(Keywords: regression)
Environment: Build version: 2.6 Build identifier: 20151218030236 Base Imade: v18D_nightly_v4 Git commit: 2015-12-17 21:29:33 2f093462 Device: flame STR: 1. Open the calendar app and create a new event 2. Tap on time for start or end time 3. Tap on top left corner to search 4. Try to type, keyboard will automatically close and will jump to select time screen and then return the the shaded search screen. Reproducible: every time
Comment 1•9 years ago
|
||
Hm this works for me on the latest dogfood ota build. Can QA reproduce?
Keywords: qawanted
Comment 2•9 years ago
|
||
Nice bug. I can reproduce this on both Flame and Aries on latest. STR is the same as comment 0. It doesn't happen every time though, and when it happens, tapping on search bar more times will eventually bring up the keyboard. Flame SEEMS to have a higher repro rate of this bug. Repro rate ~3 out of 5 on Flame. ~1 out of 5 on Aries. Could be dependent on timing or other factors. Device: Aries 2.6 BuildID: 20151221131907 Gaia: 14aefb2519becfa32f31bcc3c9c995693421f19c Gecko: a8acaa9868df4aa8d801725cfa9ef744640fc402 Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56 Version: 46.0a1 (2.6) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0 Device: Flame 2.6 BuildID: 20151221030230 Gaia: 14aefb2519becfa32f31bcc3c9c995693421f19c Gecko: e6ba2d4a2e4930bb359f90312ef6f1ebdc34c0ac Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a Version: 46.0a1 (2.6) Firmware Version: v18Dv4 User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0 ------ Unable to repro this on Flame 2.5. Repro rate 0 out of 20. Device: Flame 2.5 BuildID: 20151218180935 Gaia: eeed1451e0e48b63abe3199e4d6906adc2a762d2 Gecko: 766600655dfb1b67c380b9da4f4b19acb505a858 Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a Version: 44.0 (2.5) Firmware Version: v18Dv4 User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.5:
--- → unaffected
status-b2g-master:
--- → affected
Flags: needinfo?(jmercado)
Keywords: qawanted → regression
Comment 3•9 years ago
|
||
Let's get a window here.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
Keywords: regressionwindow-wanted
Updated•9 years ago
|
QA Contact: pcheng
Comment 4•9 years ago
|
||
I couldn't find a point in 2.6 master where this bug does not repro. So I changed direction and attempted to get a fixed window within 2.5 branch. v2.5 b2g44 reverse regression window: Last Broken Device: Flame 2.5 BuildID: 20151107112234 Gaia: 577948202ae12154524a2bd2bd6d467838ad50b8 Gecko: ae7b8b1fd9e1504347b938820f99d75058049386 Version: 44.0a2 (2.5) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0 First Working Device: Flame 2.5 BuildID: 20151109043856 Gaia: cf646c52bb947af28329b0a100df91d1b1f2a907 Gecko: 4eafef5b80f8985c94c4a067f130d37513e1a581 Version: 44.0a2 (2.5) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0 Last Broken Gaia First Working Gecko - repro Gaia: 577948202ae12154524a2bd2bd6d467838ad50b8 Gecko: 4eafef5b80f8985c94c4a067f130d37513e1a581 Last Broken Gecko First Working Gaia - no repro Gaia: cf646c52bb947af28329b0a100df91d1b1f2a907 Gecko: ae7b8b1fd9e1504347b938820f99d75058049386 Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/577948202ae12154524a2bd2bd6d467838ad50b8...cf646c52bb947af28329b0a100df91d1b1f2a907 This issue appears to have been fixed in v2.5 by the reverting done in the pushlog. The revert appears to be for bug 1207485. I assume bug 1207485 is also what broke this in the first place so putting that bug as blocking this bug.
Blocks: 1207485
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: regressionwindow-wanted
Comment 5•9 years ago
|
||
Tim this issue was fixed on 2.5 by a backout. Is it reasonable to back this out of master as well or should it be fixed in some other way?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado) → needinfo?(timdream)
Assignee | ||
Comment 6•9 years ago
|
||
Let me see what I can do. It's possible this bug can be dup to bug 1224128. Thanks for ni.
Assignee: nobody → timdream
Component: Gaia::System::Window Mgmt → Gaia::System::Input Mgmt
Flags: needinfo?(timdream)
Assignee | ||
Comment 7•9 years ago
|
||
... and yes, I can manually confirm this is a dup.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Comment 8•8 years ago
|
||
According to https://bugzilla.mozilla.org/show_bug.cgi?id=1224128#c11, I change the status to "resolved verified".
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•