Le 25/01/2016 09:50, Alexandre Lissy a écrit :
> Le 25/01/2016 04:47, Sammy Patenotte a écrit :
>> Hi Henry,
>> I just did, and didn't get any more lines of log, but I added some debug
>> statements in broadcastMessage(), and found out that the problem is in this
>> block:
>> // Buffer system messages until the webapps' registration is ready,
>> // so that we can know the correct pages registered to be broadcasted.
>> if (!this._webappsRegistryReady) {
>> this._bufferedSysMsgs.push({ how: "broadcast",
>> type: aType,
>> msg: aMessage,
>> extra: aExtra });
>> return Promise.resolve();
>> }
> You register your message handler from index.html ? And the target is
> messageHandler.html ?
>
> If so, I think we do not trigger anything in that case and we except
> registration to be done from the same page as handling.See also https://bugzilla.mozilla.org/show_bug.cgi?id=818000 Bottom line: system messages are broken if you don't use them exactly as existing apps. -- Julien
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
