Send a system message to the entry point of the application when the application is not running anymore but waits for a notification

NEW
Assigned to

Status

Firefox OS
General
5 years ago
4 years ago

People

(Reporter: vingtetun, Assigned: fabrice)

Tracking

unspecified
x86_64
Linux
Dependency tree / graph

Firefox Tracking Flags

(blocking-basecamp:-)

Details

This bug is about supporting entry_points for notifications/system messages.
I don't believe this should block the release but I could be wrong.

+++ This bug was initially created as a clone of Bug #814074 +++

When an application use the desktop notification API but is closed (because of an OOM or by a user action) the notification stays and clicking on it does nothing.

This affects the dialer and soon the sms application.

This patch use the support provided by bug 778668 to know what is the source of the notification and use system message to open it if needed, sending the title/text of the notification to the application in order to let it reposition the UI to the right state.
(Assignee)

Updated

5 years ago
blocking-basecamp: + → ?
(In reply to Vivien Nicolas (:vingtetun) from comment #0)
> This bug is about supporting entry_points for notifications/system messages.
> I don't believe this should block the release but I could be wrong.

Good enough for me to - :)  If anyone feels differently, please renom.
blocking-basecamp: ? → -
Keywords: smoketest
It affects the SMS App and furthermore the following bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=796904

It's important because we are going to launch Class 0 messages as a Notification and user should be able to click on it. It's a requirement for certification, so we should update this bug to bb+!
blocking-basecamp: - → ?

Updated

5 years ago
Assignee: nobody → fabrice
blocking-basecamp: ? → +
(In reply to Borja Salguero [:borjasalguero] from comment #2)
> It affects the SMS App and furthermore the following bug:
> https://bugzilla.mozilla.org/show_bug.cgi?id=796904
> 
> It's important because we are going to launch Class 0 messages as a
> Notification and user should be able to click on it. It's a requirement for
> certification, so we should update this bug to bb+!

SMS don't use entry points so please explain what is the relationship between this bug and class 0 message?
blocking-basecamp: + → ?
(In reply to Vivien Nicolas (:vingtetun) from comment #3)
> (In reply to Borja Salguero [:borjasalguero] from comment #2)
> > It affects the SMS App and furthermore the following bug:
> > https://bugzilla.mozilla.org/show_bug.cgi?id=796904
> > 
> > It's important because we are going to launch Class 0 messages as a
> > Notification and user should be able to click on it. It's a requirement for
> > certification, so we should update this bug to bb+!
> 
> SMS don't use entry points so please explain what is the relationship
> between this bug and class 0 message?

Borja, can you provide some info?  Thanks.
Flags: needinfo?(fbsc)
Sorry for the delay. This bug is related to 'entry_points' declared in Manifest,  I was talking about the mechanism that we need for retrieving a notification properly, but this is tracked in other bug. Sorry for the noise.
Flags: needinfo?(fbsc)
basecamp-. Please ensure that the other bug that you mentioned is nomed.
blocking-basecamp: ? → -
You need to log in before you can comment on or make changes to this bug.