Again, this is not about the system message being not delivered. This is about the notification onclick/onclose not being called.
-Michael PS: The only system message that is missed or not delivered is the "notification" system message, but this would only be a workaround for onclick/onclose anyway. On Monday, August 5, 2013 5:06:42 PM UTC+2, Etienne Segonzac wrote: > On Mon, Aug 5, 2013 at 12:05 PM, ANTONIO MANUEL AMAYA CALVO > <[email protected]>wrote: > > > > > 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 sounds like a bug :/ > > I wasn't able to reproduce it (tried by delaying the setMessageHandler for > > the telephony-new-call message in the dialer and calling in between the > > load and the setMessageHandler call, once the delay was over the app got > > the message and opened the call screen). > > > > But anyway it's probably worth filing with a simple test case. > > -- > > Etienne _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
