Closed Bug 994823 Opened 10 years ago Closed 9 years ago

[Messages] Only one notification per thread is displayed at one time

Categories

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

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1082546

People

(Reporter: julienw, Unassigned)

References

Details

(Keywords: regression)

STR:
* receive 2 SMS from the same number, with the SMS app closed

Expected:
* 2 notifications are displayed

Actual:
* 1 notification only is displayed, from the last received message

What happens is that we tag the notification with the thread id, so the older notification gets replaced by the new one, instead of having another one.

While I think it could be a good thing, I think that in that case we'd want to change the notification text, saying that there are 2 unread messages for example.

NI Omega for 2 questions:
* should we restore the previous way of working as a first step
* should we implement a smarter way of doing multiple notifications as a second step

If we want to fix the regression (from bug 855165) then it will be probably 1.4+, but I'm waiting for Omega's answer before requesting the flag.
Flags: needinfo?(ofeng)
OK, let's do this:

1 message:
[ic] %SenderName        %TimeStamp
[on] %Message

2 messages:
[ic] %SenderName        %TimeStamp
[on] 2 unread messages
Flags: needinfo?(ofeng)
Omega, I think we can't do this for 1.4 because of the string freeze, but we can definitely do this for 1.5, thanks :)

Do you want that we go back to the previous behavior for 1.4, or is the current behavior good enogh for you?
Flags: needinfo?(ofeng)
IMO, for 1.4, the current behavior is good enough. No need to go back. Thanks! :)
Flags: needinfo?(ofeng)
oki, I hope partners won't come later to block on it ;)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.