Created attachment 8518409 [details] logcat_20141106_1111.txt Description: On 2.1 on a fresh flash the user can crate a smart collection with out internet connection Repro Steps: 1) Update a Flame to 20141106001204 2) Off of a fresh flash tap through the FTU without enabling data or wifi 3) Go to settings and log into a wifi network > and go to home screen 4) Hold home button on a blank spot and tap the create new smart collection button Actual: 2.1 does not conform to the other branches Expected: 2.1's smart collections conforms all other branches Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141106001204 Gaia: 9658b93b412bdcc0f953d668e8c8e68318c99fb8 Gecko: 76880403db44 Version: 34.0 (2.1) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency:100% See attached:logcat, video clip:https://www.youtube.com/watch?v=iMhHeEJUliI
This issue DOES not occur on 2.2 (319mb)(Kitkat Base)(Shallow Flash) flame 2.0 (319mb)(Kitkat Base)(Shallow Flash) user is told cannot crate smart collection without internet connection Flame 2.2 Device: Flame 2.2 Master(319mb)(KitKat)(Shallow Flash) Build ID: 20141106043013 Gaia: 068b9711277b06c7d633517f9e1fcb5624bb39b3 Gecko: 41adad987d82 Version: 36.0a1 (2.2) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Flame 2.0 Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141105183012 Gaia: 5ee26701a4d8db266bfb203b2179f686ce14d8b6 Gecko: dbf49343e889 Version: 32.0 (2.0) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Not nominating to block. This issue only repros after a fresh flash. It can also be missed by turning on wifi or data anytime before trying to add a smart collection
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Mass update: Resolve wontfix all issues with legacy homescreens. As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.