1f13f38256147b65092678c2627a329e20380363: Bug 1348424 - Grab a reference to the window when swapping out its background color. r=spohl, a=dveditz draft
Markus Stange <mstange@themasta.com> - Thu, 23 Mar 2017 14:29:51 -0400 - rev 561537
Push 53770 by bmo:mstange@themasta.com at Wed, 12 Apr 2017 20:49:58 +0000
Bug 1348424 - Grab a reference to the window when swapping out its background color. r=spohl, a=dveditz MozReview-Commit-ID: HS1AYyxfMWS
9c32a99fff5ee797b5f2605168b4ceb0332ee6d9: Bug 1354715 - Restore the right background color. r=spohl draft
Markus Stange <mstange@themasta.com> - Fri, 07 Apr 2017 18:05:24 -0400 - rev 561536
Push 53770 by bmo:mstange@themasta.com at Wed, 12 Apr 2017 20:49:58 +0000
Bug 1354715 - Restore the right background color. r=spohl MozReview-Commit-ID: K7SF3rNPWUT
558b861d61367e9a07a118c10874f310625f540b: Bug 1302702 - Remove from ext-backgroundPage any code that uses the AddonManager object. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 16:28:15 +0100 - rev 561535
Push 53769 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:48:41 +0000
Bug 1302702 - Remove from ext-backgroundPage any code that uses the AddonManager object. The background page do not need to use the AddonManager to set its preferred debugging global anymore (and it would not be able to use it from the extension child process). MozReview-Commit-ID: 2IAxvCjDKvl
ebe8dc3d1655e19016fd5bff0ce65b075df5ec0c: Bug 1302702 - Add tests to check that ExtensionDebuggingUtils is cleaned up when the addon debugger is closed. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 15:59:54 +0100 - rev 561534
Push 53769 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:48:41 +0000
Bug 1302702 - Add tests to check that ExtensionDebuggingUtils is cleaned up when the addon debugger is closed. MozReview-Commit-ID: GZT0U1kNwr3
219eacd563dba9e96ed03a3460c32efbae56a18a: Bug 1302702 - Make WebExtension Addon Debugging oop-compatible. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 15:55:35 +0100 - rev 561533
Push 53769 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:48:41 +0000
Bug 1302702 - Make WebExtension Addon Debugging oop-compatible. This patch applies all the changes needed to the devtools actors and the toolbox-process-window, to be able to debug a webextension running in an extension child process (as well as a webextension running in the main process). The devtools actor used to debug a webextension is splitted into 3 actors: - the WebExtensionActor is the actor that is created when the "root.listTabs" RDP request is received, it provides the addon metadata (name, icon and addon id) and two RDP methods: - reload: used to reload the addon (e.g. from the "about:debugging#addons" page) - connectAddonDebuggingActor: which provides the actorID of the actor that is connected to the process where the extension is running (used by toolbox-process-window.js to connect the toolbox to the needed devtools actors, e.g. console, inspector etc.) - the WebExtensionParentActor is the actor that connects to the process where the extension is running and ensures that a WebExtensionChildActor instance is created and connected (this actor is only the entrypoint to reach the WebExtensionChildActor, and so it does not provide any RDP request on its own, it only connect itself to its child counterpart and then it returns the RDP "form" of the child actor, and the client is then connected directly to the child actor) - the WebExtensionChildActor is the actor that is running in the same process of the target extension, and it provides the same requestTypes of a tab actor. By splitting the WebExtensionActor from the WebExtensionParentActor, we are able to prevent the RemoteDebuggingServer to connect (and create instances of the WebExtensionChildActor) for every addon listed by a root.listAddons() request. MozReview-Commit-ID: L1vxhA6xQkD
b983289027ecda5a4189f035b0bcb8fc4e138569: Bug 1302702 - ExtensionParent DebugUtils xpcshell test unit. draft
Luca Greco <lgreco@mozilla.com> - Tue, 11 Apr 2017 05:13:13 +0200 - rev 561532
Push 53769 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:48:41 +0000
Bug 1302702 - ExtensionParent DebugUtils xpcshell test unit. MozReview-Commit-ID: 2wbZfQiktho
48a7f2c40e70c9e230b3fb67b3d3af6018d2027a: Bug 1302702 - Provide an ExtensionDebuggingUtils object from ExtensionParent.jsm. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 16:24:13 +0100 - rev 561531
Push 53769 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:48:41 +0000
Bug 1302702 - Provide an ExtensionDebuggingUtils object from ExtensionParent.jsm. This change prepare the WebExtensions internals to the changes applied to the addon debugging facilities in the other patches from this queue. In ExtensionParent.jsm, a HiddenXULWindow helper class has been refactored out of the HiddenExtensionPage and then reused by both HiddenExtensionPage and the new ExtensionDebuggingUtils object. The ExtensionDebuggingUtils object provides the utility methods used by the devtools actors related to the addon debugging, which are used to retrieve an "extension process browser XUL element" (a XUL browser element that has been configured by ExtensionDebuggingUtils to be used to connect the devtools parent actor to the process where the target extension is running), and then release it when it is not needed anymore (because the developer toolbox has been closed and all the devtools actors destroyed). The ExtensionDebuggingUtils object used the HiddenXULWindow class to lazily create an hidden XUL window to contain the "extension process browser XUL elements" described above (and the HiddenXULWindow istance is then destroyed when there is no devtools actor that is using it anymore). MozReview-Commit-ID: 31RYQk1DMvE
35c2222a491010bd44fbc2230adfe6da65ae089b: Bug 1354855 - Set update timer prefs in new update tests draft
Doug Thayer <dothayer@mozilla.com> - Wed, 12 Apr 2017 13:47:42 -0700 - rev 561530
Push 53768 by bmo:dothayer@mozilla.com at Wed, 12 Apr 2017 20:48:19 +0000
Bug 1354855 - Set update timer prefs in new update tests In the log file attached to this bug, we see multiple requests for background updates come in at the same time. I can't see a way for this to happen other than notify being called while the test is running. MozReview-Commit-ID: Gm0vW32X6mN
e32b06b1d4071d2309df5950ce9c7e52c6e62fb7: Bug 1302702 - Remove from ext-backgroundPage any code that uses the AddonManager object. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 16:28:15 +0100 - rev 561529
Push 53767 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:41:31 +0000
Bug 1302702 - Remove from ext-backgroundPage any code that uses the AddonManager object. The background page do not need to use the AddonManager to set its preferred debugging global anymore (and it would not be able to use it from the extension child process). MozReview-Commit-ID: 2IAxvCjDKvl
19630ef88d6484ede0fe3a2803582107fee405cc: Bug 1302702 - Add tests to check that ExtensionDebuggingUtils is cleaned up when the addon debugger is closed. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 15:59:54 +0100 - rev 561528
Push 53767 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:41:31 +0000
Bug 1302702 - Add tests to check that ExtensionDebuggingUtils is cleaned up when the addon debugger is closed. MozReview-Commit-ID: GZT0U1kNwr3
712a3a9c1f13710ec7175bed82d20ff06ebd252e: Bug 1302702 - Make WebExtension Addon Debugging oop-compatible. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 15:55:35 +0100 - rev 561527
Push 53767 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:41:31 +0000
Bug 1302702 - Make WebExtension Addon Debugging oop-compatible. This patch applies all the changes needed to the devtools actors and the toolbox-process-window, to be able to debug a webextension running in an extension child process (as well as a webextension running in the main process). The devtools actor used to debug a webextension is splitted into 3 actors: - the WebExtensionActor is the actor that is created when the "root.listTabs" RDP request is received, it provides the addon metadata (name, icon and addon id) and two RDP methods: - reload: used to reload the addon (e.g. from the "about:debugging#addons" page) - connectAddonDebuggingActor: which provides the actorID of the actor that is connected to the process where the extension is running (used by toolbox-process-window.js to connect the toolbox to the needed devtools actors, e.g. console, inspector etc.) - the WebExtensionParentActor is the actor that connects to the process where the extension is running and ensures that a WebExtensionChildActor instance is created and connected (this actor is only the entrypoint to reach the WebExtensionChildActor, and so it does not provide any RDP request on its own, it only connect itself to its child counterpart and then it returns the RDP "form" of the child actor, and the client is then connected directly to the child actor) - the WebExtensionChildActor is the actor that is running in the same process of the target extension, and it provides the same requestTypes of a tab actor. By splitting the WebExtensionActor from the WebExtensionParentActor, we are able to prevent the RemoteDebuggingServer to connect (and create instances of the WebExtensionChildActor) for every addon listed by a root.listAddons() request. MozReview-Commit-ID: L1vxhA6xQkD
9511dc6154754356b210c5f948c389bd28e38ded: Bug 1302702 - ExtensionParent DebugUtils xpcshell test unit. draft
Luca Greco <lgreco@mozilla.com> - Tue, 11 Apr 2017 05:13:13 +0200 - rev 561526
Push 53767 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:41:31 +0000
Bug 1302702 - ExtensionParent DebugUtils xpcshell test unit. MozReview-Commit-ID: 2wbZfQiktho
ad7fe3a9c9ca1e30ada78aa159f3c589f5149a62: Bug 1302702 - Provide an ExtensionDebuggingUtils object from ExtensionParent.jsm. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 16:24:13 +0100 - rev 561525
Push 53767 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:41:31 +0000
Bug 1302702 - Provide an ExtensionDebuggingUtils object from ExtensionParent.jsm. This change prepare the WebExtensions internals to the changes applied to the addon debugging facilities in the other patches from this queue. In ExtensionParent.jsm, a HiddenXULWindow helper class has been refactored out of the HiddenExtensionPage and then reused by both HiddenExtensionPage and the new ExtensionDebuggingUtils object. The ExtensionDebuggingUtils object provides the utility methods used by the devtools actors related to the addon debugging, which are used to retrieve an "extension process browser XUL element" (a XUL browser element that has been configured by ExtensionDebuggingUtils to be used to connect the devtools parent actor to the process where the target extension is running), and then release it when it is not needed anymore (because the developer toolbox has been closed and all the devtools actors destroyed). The ExtensionDebuggingUtils object used the HiddenXULWindow class to lazily create an hidden XUL window to contain the "extension process browser XUL elements" described above (and the HiddenXULWindow istance is then destroyed when there is no devtools actor that is using it anymore). MozReview-Commit-ID: 31RYQk1DMvE
4d1cfc273ef1ba975b31ca50177b05200bf85020: Bug 1249263 - add a `removeByFilter` method to filter by host,r?mak draft
milindl <i.milind.luthra@gmail.com> - Mon, 10 Apr 2017 19:56:28 +0530 - rev 561524
Push 53766 by bmo:i.milind.luthra@gmail.com at Wed, 12 Apr 2017 20:38:49 +0000
Bug 1249263 - add a `removeByFilter` method to filter by host,r?mak Added a method in History to filter by host and timeframe, which is designed to act as a replacement for `RemovePagesByTimeFrame` and `RemovePagesFromHost` in the old API. The `filter` object accepts both a host argument, as well as a timeframe, and filters as per one or both of them. MozReview-Commit-ID: 8n2AdCllv4V
56ec563e1c2c95430d012dda480b40d9a3a8155f: Bug 1353936 - Use PREF_RegisterPriorityCallback from Add*VarCache. r=froydnj draft
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Wed, 12 Apr 2017 00:17:52 +0900 - rev 561523
Push 53765 by VYV03354@nifty.ne.jp at Wed, 12 Apr 2017 20:37:17 +0000
Bug 1353936 - Use PREF_RegisterPriorityCallback from Add*VarCache. r=froydnj MozReview-Commit-ID: LOxPTBqol9X
5b7ce5b4e5a8e99c669e530759502b859198f36f: Bug 1353936 - Implement PREF_RegisterPriorityCallback. r?froydnj draft
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Wed, 12 Apr 2017 21:10:57 +0900 - rev 561522
Push 53765 by VYV03354@nifty.ne.jp at Wed, 12 Apr 2017 20:37:17 +0000
Bug 1353936 - Implement PREF_RegisterPriorityCallback. r?froydnj MozReview-Commit-ID: 1tdE6boBUVO
b470287acf2196b6ea847b2b2b2ad27ee28494e2: Bug 1352269 - Added tab scalar test and manifest file draft
John Dorlus <jdorlus@mozilla.com> - Fri, 31 Mar 2017 14:16:00 -0400 - rev 561521
Push 53764 by bmo:jdorlus@mozilla.com at Wed, 12 Apr 2017 20:36:28 +0000
Bug 1352269 - Added tab scalar test and manifest file Added test_main_ping_addon_install_tab_window_scalars.py. This test opens and closes tabs and checks that the scalars for max number of concurrent tabs, tab open events, and number of windows open are correct. It uses the addon install method to generate the ping. Testrail test case: https://testrail.stage.mozaws.net/index.php?/cases/view/4963 MozReview-Commit-ID: WUwvYnadcp
d0d0a3b0203c77ff1d2791efb821c1d0dda9cd50: Bug 1302702 - Remove from ext-backgroundPage any code that uses the AddonManager object. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 16:28:15 +0100 - rev 561520
Push 53763 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:18:17 +0000
Bug 1302702 - Remove from ext-backgroundPage any code that uses the AddonManager object. The background page do not need to use the AddonManager to set its preferred debugging global anymore (and it would not be able to use it from the extension child process). MozReview-Commit-ID: 2IAxvCjDKvl
93d0bdfb3723c98175b4bc27eb90a9dd0828d85f: Bug 1302702 - Add tests to check that ExtensionDebuggingUtils is cleaned up when the addon debugger is closed. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 15:59:54 +0100 - rev 561519
Push 53763 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:18:17 +0000
Bug 1302702 - Add tests to check that ExtensionDebuggingUtils is cleaned up when the addon debugger is closed. MozReview-Commit-ID: GZT0U1kNwr3
bebd63db5dfe3c275337b614959c1dd692585f1f: Bug 1302702 - Make WebExtension Addon Debugging oop-compatible. draft
Luca Greco <lgreco@mozilla.com> - Tue, 21 Mar 2017 15:55:35 +0100 - rev 561518
Push 53763 by luca.greco@alcacoop.it at Wed, 12 Apr 2017 20:18:17 +0000
Bug 1302702 - Make WebExtension Addon Debugging oop-compatible. This patch applies all the changes needed to the devtools actors and the toolbox-process-window, to be able to debug a webextension running in an extension child process (as well as a webextension running in the main process). The devtools actor used to debug a webextension is splitted into 3 actors: - the WebExtensionActor is the actor that is created when the "root.listTabs" RDP request is received, it provides the addon metadata (name, icon and addon id) and two RDP methods: - reload: used to reload the addon (e.g. from the "about:debugging#addons" page) - connectAddonDebuggingActor: which provides the actorID of the actor that is connected to the process where the extension is running (used by toolbox-process-window.js to connect the toolbox to the needed devtools actors, e.g. console, inspector etc.) - the WebExtensionParentActor is the actor that connects to the process where the extension is running and ensures that a WebExtensionChildActor instance is created and connected (this actor is only the entrypoint to reach the WebExtensionChildActor, and so it does not provide any RDP request on its own, it only connect itself to its child counterpart and then it returns the RDP "form" of the child actor, and the client is then connected directly to the child actor) - the WebExtensionChildActor is the actor that is running in the same process of the target extension, and it provides the same requestTypes of a tab actor. By splitting the WebExtensionActor from the WebExtensionParentActor, we are able to prevent the RemoteDebuggingServer to connect (and create instances of the WebExtensionChildActor) for every addon listed by a root.listAddons() request. MozReview-Commit-ID: L1vxhA6xQkD
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip