935785 - [B2G][Email][Notifications] Notification of grouped new emails overwrites previous Notification.

Status: RESOLVED DUPLICATE of bug 922722

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Peter Bylenga [:PBylenga]]

Description:
If user receives a second notification of grouped new messages, the notification replaces the previous notification instead of merging into a single group notification.

Repro Steps:
1) Updated Buri to Build ID: 20131106004004
2) Setup an email account via Email App with a non-manual sync period.
3) Navigate to Homescreen
4) Receive a notification for a single new email
5) Receive a second notification for a group of new emails to the same account.
6) Drag down notification bar and observe.

Actual:
There is only a single grouped new email notification that doesn’t include the first notification in its tally.

Expected:
There is only a single grouped new email notification that includes the previous notification in its tally.

Environmental Variables
Device: Buri v1.2 COM RIL
Build ID: 20131106004004
Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/6a831fcb96f4
Gaia: 2140c987fdde1c99097018f7e93b0bbd43d2125d
Platform Version: 26.0
RIL Version: 01.01.00.019.281 
Firmware Version: US_20131015

Notes:
Repro frequency: 5/5, 100%
This was discovered using Gmail

These scenarios were tested with email app in background and with it closed:
1. Receive single notification then a group notification
2. Receive group notification then another group notification
3. Receive group notification then a single notification

In all cases the first received notification was removed and the second was not updated to include the tally of the first.

Comment 1

[Jason Smith [:jsmith]]

This sounds like wrong behavior for a 1.2 feature. We're essentially incorrectly mentioning to the user how many new emails are present in the group notification use cases mentioned above.

Comment 2

[Tony Chung [:tchung]]

ni? james to comment on broken functionality or not.

Comment 3

[James Burke [:jrburke]]

This is a result of not having Notification.get() available in 1.2, which is tracked in bug 899574. That feature was not approved for koi because of concerns about the size of the change and the timing of when it landed. So until that is fixed, this behavior will be seen. We have a bug tracking the fixing of this behavior in bug 922722, but since it is dependent on the Notification.get() work, will not land until 1.3.

So closing this as a dupe of 922722, since that previous bug also has the Notification.get() bug relationship established.