Closed Bug 1111739 Opened 5 years ago Closed 4 years ago

[Smart Collections] Pulling down Notification window when creating Smart Collection will close Smart Collection menu.


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

Gonk (Firefox OS)
Not set


(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

tracking-b2g backlog
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected
b2g-master --- affected


(Reporter: jthomas, Unassigned)




(Keywords: polish, Whiteboard: [2.2-exploratory-2][systemsfe])


(1 file)

Description:If the user is half way into the process of creating a new smart collection folder, pulling down the notification menu will close the smart collection menu. 

Repro Steps:
1) Update a Flame to 20141215040201
2) From the Homescreen on an empty space long press and hold.
3) Select Add Smart Collection
4) Pull down Notification menu.

The Smart collection window that is asking the User if they want a Custom or another type of smart collection will close out when the notification menu is pulled out. 

It is expected that the Smart Collections menu will remain open even after the notification window is dropped down.

Flame 2.2

Environmental Variables:
Device: Flame 2.2 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141215040201
Gaia: e2a3e606675c346b6e6f35351a458040be599b09
Gecko: f14dcd1c8c0b
Gonk: 263b5f41f7733c5577fb101eb4dc8ac5c11cfa8d
Version: 37.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Repro frequency:100%,
See attached: Logcat & Video

Flags: needinfo?
This issue DOES occur on Flame 2.1 KK (319mb) and Flame 2.0 KK (319mb) 

Result: The Smart collection window that is asking the User if they want a Custom or another type of smart collection will close out when the notification menu is pulled down. 

Flame 2.1

Environmental Variables:
Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141215001202
Gaia: 97873dca486abf4162a3345e71b375806937bdec
Gecko: ec87f4f41d3d
Gonk: 263b5f41f7733c5577fb101eb4dc8ac5c11cfa8d
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.0

Environmental Variables:
Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141212000203
Gaia: f3b9806f687fbbd7eba6b0e1f6ebb8bde09840ea
Gecko: 32f9fae79b89
Gonk: 263b5f41f7733c5577fb101eb4dc8ac5c11cfa8d
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo? → needinfo?(dharris)
[Blocking Requested - why for this release]:

The notification screen closes out the custom smart collection window entirely. This is poor user flow. Nominating to block 2.2
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Not a regression.
blocking-b2g: 2.2? → backlog
Keywords: polish
Whiteboard: [2.2-exploratory-2] → [2.2-exploratory-2][systemsfe]
blocking-b2g: backlog → ---
This issue also occurs on 3.0 
(After bringing down the notification menu, tapping anywhere on it dismisses the smart collection window behind it)

Device: Flame 3.0 (KK - Nightly - Full Flash - 319mem)
Build ID: 20150415095209
Gaia: 2dd89fef4fae4d86fd313037ef384086c2e0e8a5
Gecko: 11077895df62
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 40.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
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.
Blocks: 1231115
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.