Closed
Bug 1183757
Opened 10 years ago
Closed 10 years ago
[Window Mgmt] Check WiFi Settings screen window will close out to Homescreen
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(b2g-v2.0 unaffected, b2g-v2.1 unaffected, b2g-v2.2 unaffected, b2g-master affected)
RESOLVED
DUPLICATE
of bug 1172167
| Tracking | Status | |
|---|---|---|
| b2g-v2.0 | --- | unaffected |
| b2g-v2.1 | --- | unaffected |
| b2g-v2.2 | --- | unaffected |
| b2g-master | --- | affected |
People
(Reporter: jthomas, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: [2.5-Daily-Testing][Spark])
Attachments
(1 file)
|
154.38 KB,
text/plain
|
Details |
Description:
After exiting the Check WiFi Settings screen the window close to Homescreen if the user selects Check Settings.
Repro Steps:
Prereq: Not connected to WiFi.
1) Update a Flame to 20150714010206
2) Open Browser
3) Enter text (Check Settings Menu appears)
4) Press Check Settings
5) Wait +5 seconds OR select WiFi to close the page out faster.
Actual:
WiFi Settings closes out to Homescreen.
Expected:
It is expected that the user will be remain on the WiFi settings page and be able to adjust them accordingly.
Environmental Variables:
Device: Flame 2.5 Kk Full Flash (319mb)
Build ID: 20150714010206
Gaia: 7676b68b4d32ed13243eeb719188847121bd5611
Gecko: 0931671a14ef
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 42.0a1 (2.5)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Repro frequency: 100%
See attached: Logcat & Video
| Reporter | ||
Comment 1•10 years ago
|
||
This issue does NOT occur on the Aries 2.5, Flame 2.2, 2.1 and 2.0.
Environmental Variables:
Device: Aries 2.5 Kk
Build ID: 20150619225606
Gaia: 4c06ed88ddccaba8dc941e5006bd2a9e57306f07
Gecko: 7c1a6b1151a1539186b950a144387e2d7f378d1b
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 41.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Environmental Variables:
Device: Flame 2.2 Kk Full Flash (319mb)
Build ID: 20150714002501
Gaia: 84d0c76370dcd3d25813b00de55194730884355b
Gecko: a5db6d9850f6
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
Environmental Variables:
Device: Flame 2.1 Kk Full Flash (319mb)
Build ID: 20150714001203
Gaia: d13826b20b4a45e3f5cd4b25a30a737d8be7f1b9
Gecko: 92049b3c4bb5
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Environmental Variables:
Device: Flame 2.0 Kk Full Flash (319mb)
Build ID: 20150714000206
Gaia: b16ba05481e577bc644ed8966f587a70fe2148e6
Gecko: 43b0dbfbf82b
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → unaffected
status-b2g-v2.1:
--- → unaffected
status-b2g-v2.2:
--- → unaffected
status-b2g-master:
--- → affected
Flags: needinfo?(ktucker)
Keywords: regression
Whiteboard: [2.5-Daily-Testing][Spark]
Comment 2•10 years ago
|
||
Can you check the Flame on master at 512mb?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(jthomas)
| Reporter | ||
Comment 3•10 years ago
|
||
This issue is NOT occurring on Flame 2.5 with 512mb. So far I am only seeing it on 319mb.
Environmental Variables:
Device: Flame 2.5 Kk Full Flash (512mb)
Build ID: 20150715010202
Gaia: c6ef08964711f461a8e6326eae911789d1ec220c
Gecko: c95ebeebbc5d
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 42.0a1 (2.5)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(jthomas) → needinfo?(ktucker)
Comment 4•10 years ago
|
||
I believe this is related to the memory regression on master. Please keep an eye out on this bug and feel free to reopen this if it still happens after the memory regression has been resolved.
Status: NEW → RESOLVED
Closed: 10 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(jthomas)
Resolution: --- → DUPLICATE
| Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(jthomas)
You need to log in
before you can comment on or make changes to this bug.
Description
•