Bug 1291715 - Add RTCDTMFSender and RTCDTMFToneChangeEvent to webidl; r=smaug MozReview-Commit-ID: FvAp6DQex02

Bug 1156427 - Fix test_set_location_through_execute_script by waiting for the page to be loaded. r?ato

Bug 1260552 - Fix clipboard and context menu tests;r=honza MozReview-Commit-ID: CxG2pVikq3g

Bug 1260552 - Fixing test failures; r=pbro MozReview-Commit-ID: G4WQq9FPzaO

Bug 1260552 - Replace xul:spliter by html:splitter; r=pbro MozReview-Commit-ID: LlWKoZGT5Z0

Bug 1260552 - Implement Splitter React component; r=jlongster, pbro MozReview-Commit-ID: LeMSMNO5UnN

Bug 1263458 - Force a full-page snapshot to make sure the scrollbars get included as well. r?botond The reftest-no-flush avoids some issues on Fennec where the reftest harness gets into an infinite loop of snapshotting because the pending-paint flag never gets cleared. The flag seems to be set as a result of the APZ flush and I'm unclear on why it doesn't get cleared normally, but this bypasses the problem. MozReview-Commit-ID: 8SGoSkRo5nm

Bug 1263458 - Force a full-page snapshot to make sure the scrollbars get included as well. r?botond The reftest-no-flush avoids some issues on Fennec where the reftest harness gets into an infinite loop of snapshotting because the pending-paint flag never gets cleared. The flag seems to be set as a result of the APZ flush and I'm unclear on why it doesn't get cleared normally, but this bypasses the problem. MozReview-Commit-ID: 9H23iylOAm3

Bug 1287007 - Move native messaging to child process Move `runtime.connectNative` and `runtime.sendNativeMessage` to `addon_child`. Note: This does not change the behavior for launching the native app, it is still launched from the main process. Some other significant changes: ExtensionUtils.Port: - Refactor Port in ExtensionUtils to allow using Port without wrappers via `registerOnMessage` and `registerOnDisconnect`. - Add "port" parameter to Port's `onMessage` method (Chrome compat). - Do not clone the message received by Port's `onMessage` (per & Chrome compat). ExtensionUtils.Messenger - Add connectGetRawPort to allow `postMessage` with already-sanitized values without having to use `cloneInto` with `context.cloneScope`. Native messaging: - Do not throw an error when `disconnect()` is called on an already-disconnected port (Chrome compat). - Do not dispatch `onDisconnect` when `.disconnect()` was called (Chrome compat). - Use `context.extension` instead of passing the extension separately. - Serialize the message in the child instead of the main process. MozReview-Commit-ID: FJUJYSb3A81

Bug 1287007 - Make window.close in extension pages async Test coverage by tabs.onRemoved + window.close() in: toolkit/components/extensions/test/mochitest/test_ext_tab_teardown.html MozReview-Commit-ID: 7asg2XGrTaQ

Bug 1287007 - Remove .contentWindow from ProxyContext MozReview-Commit-ID: ASNigrM07yz

Bug 1287007 - Fix test_ext_management_uninstall_self.js The test logic was broken by design: Two tests uninstall the addon, but only one uninstall observer was used. Consequently, the second test resumes the test before the addon was actually uninstalled. It is probably sheer luck that the test worked before. MozReview-Commit-ID: DcT48ZQ2bRp

Bug 1287007 - Enable proxying of most APIs. MozReview-Commit-ID: KrI42XrsVVG

Bug 1287007 - Fix timing issue in test_ext_storage.js MozReview-Commit-ID: 63Ra7ThuHuf

Bug 1287007 - Fix "onclick" in contextMenus, to child. Main thing: Making contextMenus implementation webext-oop compatible. Preparation: - Add getParentEvent to ChildAPIManager to allow use of remote events. - Introduce `addon_parent_only` "restriction" to only generate a schema API in the main process. - Do not fill in `null` for missing keys if the schema declares a key as `"optional": "omit-key-if-missing"`. This is needed for the second point in the next list. Drive-by fixes: - Ensure that the "onclick" handler is erased when a context closes. - Do not clear the "onclick" handler in `contextMenus.update` if the onclick key has been omitted (parity with Chrome). - Remove some unnecessary `Promise.resolve()` - Add extensive set of tests that check the behavior of the contextMenus APIs with regards to the onclick attribute in various scenarios. MozReview-Commit-ID: A5f3AUQzU8T

Bug 1287007 - Move native messaging to child process Move `runtime.connectNative` and `runtime.sendNativeMessage` to `addon_child`. Note: This does not change the behavior for launching the native app, it is still launched from the main process. Some other significant changes: ExtensionUtils.Port: - Refactor Port in ExtensionUtils to allow using Port without wrappers via `registerOnMessage` and `registerOnDisconnect`. - Add "port" parameter to Port's `onMessage` method (Chrome compat). - Do not clone the message received by Port's `onMessage` (per & Chrome compat). ExtensionUtils.Messenger - Add connectGetRawPort to allow `postMessage` with already-sanitized values without having to use `cloneInto` with `context.cloneScope`. Native messaging: - Do not throw an error when `disconnect()` is called on an already-disconnected port (Chrome compat). - Do not dispatch `onDisconnect` when `.disconnect()` was called (Chrome compat). - Use `context.extension` instead of passing the extension separately. - Serialize the message in the child instead of the main process. MozReview-Commit-ID: FJUJYSb3A81

Bug 1287007 - Make window.close in extension pages async Test coverage by tabs.onRemoved + window.close() in: toolkit/components/extensions/test/mochitest/test_ext_tab_teardown.html MozReview-Commit-ID: 7asg2XGrTaQ

Bug 1287007 - Remove .contentWindow from ProxyContext MozReview-Commit-ID: ASNigrM07yz

Bug 1287007 - Fix test_ext_management_uninstall_self.js The test logic was broken by design: Two tests uninstall the addon, but only one uninstall observer was used. Consequently, the second test resumes the test before the addon was actually uninstalled. It is probably sheer luck that the test worked before. MozReview-Commit-ID: DcT48ZQ2bRp

Bug 1287007 - Enable proxying of most APIs. MozReview-Commit-ID: KrI42XrsVVG