On 05/08/2013, at 11:15, "Etienne Segonzac" <[email protected]> wrote:
> On Mon, Aug 5, 2013 at 10:18 AM, Michael Diener < > [email protected]> wrote: > >> Thanks Antonio, but the system messages are delivered successfully in my >> case. > > Yep, gecko queues the messages waiting for the message handler to be set. > If the app isn't running, it does. If the app is running/the handler page is loaded, it doesn't. You can try it easily enough by setting a delay between loading the app and setting the handler. Then load the app and before the delay expires send a message to the app. That message will be lost. This sounded similar to what Michael was describing :). Best, Antonio > >> >> When they are delivered, the endpoint page is not yet in memory and gets >> loaded successfully so the message handlers are triggered. Then my code in >> that handler acquires a wakelock and displays a notification. This >> notification is successfully displayed, but onclick is not called when >> clicking the notification. > > You should be able to register for the "notification" system message in > order to be notified of the notification click even if your app got killed > (and the notification.onlick handler gced). > -- > Etienne > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
