803935 - Support marking a notification as "read", directly from the parent App

Status: RESOLVED FIXED

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

Description

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

STR
 (1) Receive SMS
 (2) Tap notification to open SMS app
 (3) Receive more SMSes while in SMS conversation screen

Notifications of the additional SMSes continue to pile up in the system tray, even though the full messages are appearing right in front of me.

Comment 1

[Rafael Rebolleda]

Notifications should still be valuable if they don't belong to the current thread the user is viewing. I agree they shouldn't be displayed for the thread on screen.

Comment 2

[Borja Salguero [:borjasalguero]]

Currently if the received sms belongs to the thread that we are into, notification does not appear. Probably the key point would be having the capability of 'removing' the notifications that have been checked directly in the APP.

Scenario:
- We are in SMS App, thread for phone number A
- We receive a SMS from A (no notification is created due to we are in the thread for number A)
- We receive a SMS from B (notification appears)
- In SMS App we move from A to B

Expected:
- Notification from B should be removed from the notification bar (check this behaviour in 'What's up' App for example)

Currently:
- Notification will be in notification bar until 'clicking' directly on it, or 'deleting' all notifications.

However this is not a problem of SMS App, is a platform problem. What about changing the name of this bug to 'B2G Notifications: Removing a notification directly from the Apps is not supported'?

Comment 3

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

If the SMS app is in the foreground, why would it ever create a notification?

Comment 4

[Borja Salguero [:borjasalguero]]

Because you have to be notified that a message from other sender has been received. It was checked with UX Team and it's the same way of working as other 'messaging' apps as 'What's up'.

Comment 5

[Josh Carpenter [:jcarpenter]]

(In reply to Borja Salguero [:borjasalguero] (limited access to email until 10th December) from comment #2)

> Expected:
> - Notification from B should be removed from the notification bar (check
> this behaviour in 'What's up' App for example)
> 
> Currently:
> - Notification will be in notification bar until 'clicking' directly on it,
> or 'deleting' all notifications.
> 
> However this is not a problem of SMS App, is a platform problem. What about
> changing the name of this bug to 'B2G Notifications: Removing a notification
> directly from the Apps is not supported'?

Done. Updated the title to: 
"Support marking a notification as "read", directly from the parent App."

Comment 6

[Josh Carpenter [:jcarpenter]]

Borja, this is marked UX-P2 ("should fix"). Can Rafa and yourself decide whether or not to nominate this for blocking-basecamp, and if you do nominate, please also be sure to add a rationale for the triagers?

Comment 7

[Borja Salguero [:borjasalguero]]

I think that this bug has a lot of implications in 'Notifications API'. We are going to request more info from Vivien.

Comment 8

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

In order to 'close' the notification we need bug 779213 that is bb- or the full implementation of the web notification API (which is out of the scope for v1).

Comment 9

[(inactive after 6/18) Alive Kuo [:alive]]

This one seems to be fixed, at least for sms app.
However make every app using notification API to detect visibilitychange sounds weird. Let's revisit the notification API implementation after v1.