1024479 - Notifications remain after tapping on them

Status: RESOLVED DUPLICATE of bug 1024090

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

Description

[Chris Lord [:cwiiis]]

It seems all notifications persist after tapping on them now, they have to be swiped away to disappear.

This happens at least for:

- Screenshots
- E-mails
- Text messages

Note, tapping on a notification works as expected (launched the app and displays the relevant item), just the notification also stays.

Sometimes tapping e-mail notifications doesn't bring the e-mail app to the foreground, but I suppose that's a separate bug (and seems to happen in 1.4 too).

Comment 1

[:gerard-majax]

(In reply to Chris Lord [:cwiiis] from comment #0)
> It seems all notifications persist after tapping on them now, they have to
> be swiped away to disappear.
> 
> This happens at least for:
> 
> - Screenshots
> - E-mails
> - Text messages
> 
> Note, tapping on a notification works as expected (launched the app and
> displays the relevant item), just the notification also stays.
> 
> Sometimes tapping e-mail notifications doesn't bring the e-mail app to the
> foreground, but I suppose that's a separate bug (and seems to happen in 1.4
> too).

I don't have any issue with the Messages notifications on my devices. Screenshots and Emails do not manage notifications the same way:
 - tapping the screenshot will show a preview of it
 - email app is not closing notifications but it is my understanding that this is done on purpose.

Comment 2

[:gerard-majax]

Now that I'm reproducing bug 1024090, I suspect there are high chances this one is a dupe.

Comment 3

[Julien Wajsberg [:julienw]]

Chris, can you please confirm that you had the issue in v2.0? I guess you're the one who set the "affected" flag for v2.0 since I don't see any change in the bug history.

Comment 4

[Chris Lord [:cwiiis]]

(In reply to Julien Wajsberg [:julienw] (away June 21 to 30) from comment #3)
> Chris, can you please confirm that you had the issue in v2.0? I guess you're
> the one who set the "affected" flag for v2.0 since I don't see any change in
> the bug history.

I thought I did, but I'm not certain - perhaps this was on a build just past the branch date(?)

Comment 5

[Julien Wajsberg [:julienw]]

The branch date was June 9th. You reported the bug June 12th. Too bad you didn't put the gecko+gaia hashes ;)