forked from mirrors/gecko-dev
ca2c1cf947
This should have been a part of bug 1298810, but that only set the argument for native messaging ports, which does not use Port from ExtensionUtils. The port parameter must also be included in runtime's Port.onMessage to avoid regressions when the port implementations are unified and native messaging starts using runtime's Port. Note that starting from this commit, multiple onMessage listeners receive the same (cloned) message instead of a new clone per listener. This is a side effect of using `fire.withoutClone` instead of `fire`: `fire` clones all parameters, but ports are not cloneable so we have to use `fire.withoutClone` instead. This change with regards to message cloning is fully compatible with Chrome's messaging API (which also passes the same message object to all `port.onMessage` calls). MozReview-Commit-ID: AUDuUKHkXCM --HG-- extra : rebase_source : b91d701bba21f376935961a6eeb1a8489ac5591b |
||
|---|---|---|
| .. | ||
| schemas | ||
| test | ||
| .eslintrc.js | ||
| ext-bookmarks.js | ||
| ext-browserAction.js | ||
| ext-c-browserAction.js | ||
| ext-c-contextMenus.js | ||
| ext-c-pageAction.js | ||
| ext-c-tabs.js | ||
| ext-commands.js | ||
| ext-contextMenus.js | ||
| ext-desktop-runtime.js | ||
| ext-history.js | ||
| ext-pageAction.js | ||
| ext-tabs.js | ||
| ext-utils.js | ||
| ext-windows.js | ||
| extension-mac-panel.css | ||
| extension-mac.css | ||
| extension-win-panel.css | ||
| extension.css | ||
| extension.svg | ||
| extensions-browser.manifest | ||
| jar.mn | ||
| moz.build | ||
