searching for reviewer(kmag)
732d6918f5bbd8578d623e07c643512296ea4706: Bug 1648590 - Set the crash report remote annotation when we set the remote type. r=kmag
Andrew McCreight <continuation@gmail.com> - Fri, 10 Jul 2020 01:56:13 +0000 - rev 539728
Push 37585 by nbeleuzu@mozilla.com at Fri, 10 Jul 2020 09:48:19 +0000
Bug 1648590 - Set the crash report remote annotation when we set the remote type. r=kmag This patch moves the remote type crash annotation code from RecvSetProcessSandbox() to RecvRemoteType(), where we actually set the remote type. This matters because RecvSetProcessSandbox() only happens once when the process is created. If the process is a preallocated process, it will get its remote type updated later, so we need to also update the annotation. It seems odd that we were setting the remote type annotation in a method related to the sandbox and not where we set the remote type. My only guess is that prior to bug 1332522 RecvSetProcessSandbox() happened first, so maybe they wanted to make sure the annotation was set as early as possible. At that point in time, the remote type never changed, so it was okay to just set it wherever, as early as possible. Anyways, after that bug, the first call to RecvRemoteType() happens earlier, so this change is strictly better. I also fixed a typo in ContentParent. Differential Revision: https://phabricator.services.mozilla.com/D82625
4c0909f105b2f8e714dbc8991391045f1a36dd6f: Bug 1648590 - Set the crash report remote annotation when we set the remote type. r=kmag
Andrew McCreight <continuation@gmail.com> - Wed, 08 Jul 2020 00:48:43 +0000 - rev 539713
Push 37585 by nbeleuzu@mozilla.com at Fri, 10 Jul 2020 09:48:19 +0000
Bug 1648590 - Set the crash report remote annotation when we set the remote type. r=kmag This patch moves the remote type crash annotation code from RecvSetProcessSandbox() to RecvRemoteType(), where we actually set the remote type. This matters because RecvSetProcessSandbox() only happens once when the process is created. If the process is a preallocated process, it will get its remote type updated later, so we need to also update the annotation. It seems odd that we were setting the remote type annotation in a method related to the sandbox and not where we set the remote type. My only guess is that prior to bug 1332522 RecvSetProcessSandbox() happened first, so maybe they wanted to make sure the annotation was set as early as possible. At that point in time, the remote type never changed, so it was okay to just set it wherever, as early as possible. Anyways, after that bug, the first call to RecvRemoteType() happens earlier, so this change is strictly better. I also fixed a typo in ContentParent. Differential Revision: https://phabricator.services.mozilla.com/D82625
f568bf729072c49ef1cf92b53e2bfed44046ae17: Bug 1650837 - Part 7: Include message name in error when pending queries are rejected, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:14:04 +0000 - rev 539473
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1650837 - Part 7: Include message name in error when pending queries are rejected, r=kmag This improves the usability of the exceptions produced in this situation. Differential Revision: https://phabricator.services.mozilla.com/D82614
cbc811712a2400783ab908a2255a1e28e6e0e152: Bug 1650837 - Part 6: Hack around SpecialPowers being disabled, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:08:03 +0000 - rev 539472
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1650837 - Part 6: Hack around SpecialPowers being disabled, r=kmag The pref is automatically disabled when disabling unsigned extensions, which can cause issues. This hacks around that issue in the one place which I noticed doing that. Differential Revision: https://phabricator.services.mozilla.com/D82613
6b119cf7128250dc51210f021d4b4d8295c88f84: Bug 1650837 - Part 5: Avoid creating new windows for every JSActor test, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:02:59 +0000 - rev 539471
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1650837 - Part 5: Avoid creating new windows for every JSActor test, r=kmag This is no longer necessary, as we now tear down the previously registered window actors when they're unregistered. Differential Revision: https://phabricator.services.mozilla.com/D82452
e28575cd2ec2fed5b9af0451f3b1002f0e148d9c: Bug 1650837 - Part 4: Add tests for JSProcessActor filtering, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:02:52 +0000 - rev 539470
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1650837 - Part 4: Add tests for JSProcessActor filtering, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82451
a14f2e220852af610b824cb667901160296686cb: Bug 1650837 - Part 3: Destroy active actors when they are unregistered, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:02:50 +0000 - rev 539469
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1650837 - Part 3: Destroy active actors when they are unregistered, r=kmag This is needed specifically for tests, which need to be able to unregister & re-register the same actor with different configuration options. With JSWindowActors, we can create new windows after each actor is unregistered, but we can't do this with in-process JSProcessActors. Differential Revision: https://phabricator.services.mozilla.com/D82450
968555d641c6a7f4e1912c0021bbe383630f85a4: Bug 1650837 - Part 2: Add an includeParent JSProcessActor config option, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:02:48 +0000 - rev 539468
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1650837 - Part 2: Add an includeParent JSProcessActor config option, r=kmag This is similar to JSWindowActor's includeChrome option, and defaults to 'false'. If users want to also instantiate the actor in-process, they can set this option to 'true'. Differential Revision: https://phabricator.services.mozilla.com/D82449
3d4556d1449c36541c3a680dcac424ccebb8b369: Bug 1650837 - Part 1: Fix broken JSProcessActor remoteType filtering, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:02:45 +0000 - rev 539467
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1650837 - Part 1: Fix broken JSProcessActor remoteType filtering, r=kmag Previously this option wasn't correctly copied from the WebIDL configuration object, meaning that it was always ignored. Differential Revision: https://phabricator.services.mozilla.com/D82448
33bcefd7800037dec75d0f419eaccbb1e38218b5: Bug 1649879 - Handle URIFixup that happens on a failed channel in DocumentLoadListener if available, rather than waiting for it to reach nsDocShell. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Wed, 08 Jul 2020 23:38:22 +0000 - rev 539455
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1649879 - Handle URIFixup that happens on a failed channel in DocumentLoadListener if available, rather than waiting for it to reach nsDocShell. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D81947
9ca98f13b6b87490601be7814a11d64597290cef: Bug 1649879 - Remove URIFixupChild. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Wed, 08 Jul 2020 23:37:59 +0000 - rev 539454
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1649879 - Remove URIFixupChild. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D81946
b0e4bfaf5370cbefdbc6831dcf4e1ba3af6e07f2: Bug 1649879 - Implement WebNavigationFlagsToFixupFlags in C++ so that we avoid needing to call into the URIFixup JS module. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Wed, 08 Jul 2020 23:37:42 +0000 - rev 539453
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1649879 - Implement WebNavigationFlagsToFixupFlags in C++ so that we avoid needing to call into the URIFixup JS module. r=kmag This should be the exact same code, just avoiding needing to create the URIFixup service in order to run it. Differential Revision: https://phabricator.services.mozilla.com/D81945
280e5d62cd74f312174d909bb720af873cb5db3e: Bug 1649879 - Don't create nsIURIFixupInfo in content process nsDocShellLoadState construction. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Wed, 08 Jul 2020 23:37:29 +0000 - rev 539452
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1649879 - Don't create nsIURIFixupInfo in content process nsDocShellLoadState construction. r=kmag Rather than constructing an nsIURIFixupInfo from the IPC call return valuess, and then immediately querying the same data, this just use the results directly. It also moves the firing of "keyword-uri-fixup" observers to the parent process side. As far as I can tell, the only consumer was URIFixupChild, which was also forwarding them to the parent process. Differential Revision: https://phabricator.services.mozilla.com/D81944
9820dc5ac04ee669e38ab0acabcf4cf660cd9aee: Bug 1649879 - Fold GetFixupURIInfo into the calling code. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Wed, 08 Jul 2020 23:37:17 +0000 - rev 539451
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1649879 - Fold GetFixupURIInfo into the calling code. r=kmag This should be a no-op change, just to make the next patch a small diff. Differential Revision: https://phabricator.services.mozilla.com/D81943
f6373dd0caa09cf46d7dc22cafe4b08db7d5b33f: Bug 1648109 - Report GetActor exceptions directly to the JSContext, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 21:17:17 +0000 - rev 539433
Push 37580 by malexandru@mozilla.com at Thu, 09 Jul 2020 04:03:58 +0000
Bug 1648109 - Report GetActor exceptions directly to the JSContext, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82446
5907260fa4688e06eb4b07982ed23fc2d476d8e3: Bug 1649477 - Part 4: Improve a couple of error messages, r=kmag
Nika Layzell <nika@thelayzells.com> - Wed, 08 Jul 2020 14:22:23 +0000 - rev 539381
Push 37579 by dluca@mozilla.com at Wed, 08 Jul 2020 21:49:35 +0000
Bug 1649477 - Part 4: Improve a couple of error messages, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82103
d7810f45f0cbbf63ec61112e4d5c16433640775b: Bug 1649477 - Part 3: Handle ReceiveRawMessage generically, r=kmag
Nika Layzell <nika@thelayzells.com> - Wed, 08 Jul 2020 14:22:22 +0000 - rev 539380
Push 37579 by dluca@mozilla.com at Wed, 08 Jul 2020 21:49:35 +0000
Bug 1649477 - Part 3: Handle ReceiveRawMessage generically, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82102
d3c935827ef7694b50f5b2d9fc2665d27f9c27c2: Bug 1649477 - Part 2: Unify JSActor manager logic, r=kmag
Nika Layzell <nika@thelayzells.com> - Wed, 08 Jul 2020 14:22:22 +0000 - rev 539379
Push 37579 by dluca@mozilla.com at Wed, 08 Jul 2020 21:49:35 +0000
Bug 1649477 - Part 2: Unify JSActor manager logic, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82101
0ad359f8308b0c853822d9033276a80827e7df47: Bug 1649477 - Part 1: Move JSActor related files into their own directory, r=kmag
Nika Layzell <nika@thelayzells.com> - Wed, 08 Jul 2020 14:22:22 +0000 - rev 539378
Push 37579 by dluca@mozilla.com at Wed, 08 Jul 2020 21:49:35 +0000
Bug 1649477 - Part 1: Move JSActor related files into their own directory, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82100
3c5bdf16febd8557a5201d49529c19e539b7dd0e: Bug 1640427 - Don't perform flaky process launch check during test, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:25:25 +0000 - rev 539221
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1640427 - Don't perform flaky process launch check during test, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82108
28af275956bd9fe75545db2d278ed80da18e8f0d: Bug 1458043 - Stop converting promises to nsISupports in xpconnect, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 07 Jul 2020 22:20:01 +0000 - rev 539219
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1458043 - Stop converting promises to nsISupports in xpconnect, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82616
830aa93d2b0c39aeb42b5157eed8e965b0a6c083: Bug 1649477 - Part 4: Improve a couple of error messages, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 20:27:13 +0000 - rev 539213
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1649477 - Part 4: Improve a couple of error messages, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82103
eca6e9dce450e6e9f5f023dc8feadb31fa50192b: Bug 1649477 - Part 3: Handle ReceiveRawMessage generically, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 20:27:11 +0000 - rev 539212
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1649477 - Part 3: Handle ReceiveRawMessage generically, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82102
5b217aa88289d7f6a9766cef24649e43470052ee: Bug 1649477 - Part 2: Unify JSActor manager logic, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 20:27:08 +0000 - rev 539211
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1649477 - Part 2: Unify JSActor manager logic, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82101
8959d02b840f97944c8383bcff1363431ef8e9fb: Bug 1649477 - Part 1: Move JSActor related files into their own directory, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 20:27:04 +0000 - rev 539210
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1649477 - Part 1: Move JSActor related files into their own directory, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82100
2e058695addc755f908cd164ef1c7fca7d527eb7: Bug 1599579 - Part 7: Fix failing contentscript test, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 19:45:48 +0000 - rev 539208
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1599579 - Part 7: Fix failing contentscript test, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82098
a89a0e4bb31e585e94685a0c245cae3982b55e4f: Bug 1599579 - Part 5: Ensure all views have matching BrowsingContextGroup IDs in getViews test, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 19:45:43 +0000 - rev 539206
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1599579 - Part 5: Ensure all views have matching BrowsingContextGroup IDs in getViews test, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D80258
4c1d7b36f0359ad66c5c0f12530ad4ea198ae6a2: Bug 1599579 - Part 4: Expose BrowsingContextGroup.id to JS, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 19:45:41 +0000 - rev 539205
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1599579 - Part 4: Expose BrowsingContextGroup.id to JS, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D80257
871123e639a8051612cbe643f2c668a5d11660c8: Bug 1599579 - Part 3: Load toplevel extension frames into a per-extension BrowsingContextGroup, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 19:45:39 +0000 - rev 539204
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1599579 - Part 3: Load toplevel extension frames into a per-extension BrowsingContextGroup, r=kmag This is done by tracking a specific BrowsingContextGroup ID on the WebExtensionPolicy in the parent process. Whenever a load is done with that policy, the browsing context is replaced to ensure it is loaded in the correct BrowsingContextGroup. This patch also ensures that extension iframes are always loaded in the same process as their embedder document, even if the frame was previously remote. Differential Revision: https://phabricator.services.mozilla.com/D80256
8ae775aac9f7a9447b73424d26f4768d9e6add65: Bug 1599579 - Part 1: Add the ability to specify a specific BrowsingContextGroup during process switch, r=kmag
Nika Layzell <nika@thelayzells.com> - Mon, 06 Jul 2020 20:10:43 +0000 - rev 539202
Push 37578 by btara@mozilla.com at Wed, 08 Jul 2020 09:42:17 +0000
Bug 1599579 - Part 1: Add the ability to specify a specific BrowsingContextGroup during process switch, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D80254
4f83cf116474c340d45771671fa4262bc4c9ec6e: Bug 1647109 - Set the child history as in process when the BC is in process r=kmag
Paul Bone <pbone@mozilla.com> - Tue, 07 Jul 2020 01:10:01 +0000 - rev 539029
Push 37576 by ncsoregi@mozilla.com at Tue, 07 Jul 2020 09:47:47 +0000
Bug 1647109 - Set the child history as in process when the BC is in process r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82367
5668e7d835af13882aa26e54cfa33b21a32314c1: Bug 1581500 - Don't assert if there are multiple process switches in-flight, since we don't do anything to prevent this. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 06 Jul 2020 19:31:33 +0000 - rev 538986
Push 37576 by ncsoregi@mozilla.com at Tue, 07 Jul 2020 09:47:47 +0000
Bug 1581500 - Don't assert if there are multiple process switches in-flight, since we don't do anything to prevent this. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D82309
f9670eed4ac5382cf1c67115426645d10fb14c6c: Bug 1649879 - Handle URIFixup that happens on a failed channel in DocumentLoadListener if available, rather than waiting for it to reach nsDocShell. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 06 Jul 2020 04:29:33 +0000 - rev 538853
Push 37573 by dluca@mozilla.com at Mon, 06 Jul 2020 16:32:20 +0000
Bug 1649879 - Handle URIFixup that happens on a failed channel in DocumentLoadListener if available, rather than waiting for it to reach nsDocShell. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D81947
76ab8adad34b34fcbd4cb13f469f809dd96d8e0e: Bug 1649879 - Remove URIFixupChild. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 06 Jul 2020 04:29:16 +0000 - rev 538852
Push 37573 by dluca@mozilla.com at Mon, 06 Jul 2020 16:32:20 +0000
Bug 1649879 - Remove URIFixupChild. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D81946
6dc2e9474f433eedcac13db9322a9c3d21dd82d9: Bug 1649879 - Implement WebNavigationFlagsToFixupFlags in C++ so that we avoid needing to call into the URIFixup JS module. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 06 Jul 2020 04:29:08 +0000 - rev 538851
Push 37573 by dluca@mozilla.com at Mon, 06 Jul 2020 16:32:20 +0000
Bug 1649879 - Implement WebNavigationFlagsToFixupFlags in C++ so that we avoid needing to call into the URIFixup JS module. r=kmag This should be the exact same code, just avoiding needing to create the URIFixup service in order to run it. Differential Revision: https://phabricator.services.mozilla.com/D81945
6f905d33681f49ec93da71b7f0774ffd146595c5: Bug 1649879 - Don't create nsIURIFixupInfo in content process nsDocShellLoadState construction. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 06 Jul 2020 04:29:06 +0000 - rev 538850
Push 37573 by dluca@mozilla.com at Mon, 06 Jul 2020 16:32:20 +0000
Bug 1649879 - Don't create nsIURIFixupInfo in content process nsDocShellLoadState construction. r=kmag Rather than constructing an nsIURIFixupInfo from the IPC call return valuess, and then immediately querying the same data, this just use the results directly. It also moves the firing of "keyword-uri-fixup" observers to the parent process side. As far as I can tell, the only consumer was URIFixupChild, which was also forwarding them to the parent process. Differential Revision: https://phabricator.services.mozilla.com/D81944
13b19e14a3320a6895eeeb941693deb3a7de891f: Bug 1649879 - Fold GetFixupURIInfo into the calling code. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 06 Jul 2020 04:29:04 +0000 - rev 538849
Push 37573 by dluca@mozilla.com at Mon, 06 Jul 2020 16:32:20 +0000
Bug 1649879 - Fold GetFixupURIInfo into the calling code. r=kmag This should be a no-op change, just to make the next patch a small diff. Differential Revision: https://phabricator.services.mozilla.com/D81943
fe77c77e6825b7b344e27b35ce09a97976b68afa: Bug 1647425 - part1 : dispatch chrome event to owner doc. r=kmag
alwu <alwu@mozilla.com> - Wed, 01 Jul 2020 21:36:25 +0000 - rev 538322
Push 37561 by ncsoregi@mozilla.com at Thu, 02 Jul 2020 09:46:06 +0000
Bug 1647425 - part1 : dispatch chrome event to owner doc. r=kmag We handle `GloballyAutoplayBlocked` event in `Autoplay` actors which exist in all frames [1], so we can actually dispatch the event directly from any document. Then, we would find the correct top document in `AutoplayParentActor`[2]. [1] https://searchfox.org/mozilla-central/rev/5a4aaccb28665807a6fd49cf48367d47fbb5a19a/toolkit/modules/ActorManagerParent.jsm#118-130 [2] https://searchfox.org/mozilla-central/source/toolkit/actors/AutoplayParent.jsm#11-18 Differential Revision: https://phabricator.services.mozilla.com/D81764
f0e47b29f8c4840d9f9fbe971991f86179b55314: Bug 1630176 - Fix the race between process switching and the new browser window loading code, r=kmag
Anny Gakhokidze <agakhokidze@mozilla.com> - Tue, 30 Jun 2020 20:57:52 +0000 - rev 538121
Push 37557 by abutkovits@mozilla.com at Wed, 01 Jul 2020 03:27:11 +0000
Bug 1630176 - Fix the race between process switching and the new browser window loading code, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D81563
c5bc0ea4219383c7da69f1968291b76d71791871: Bug 1599579 - Part 5: Ensure all views have matching BrowsingContextGroup IDs in getViews test, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 30 Jun 2020 15:55:47 +0000 - rev 538049
Push 37557 by abutkovits@mozilla.com at Wed, 01 Jul 2020 03:27:11 +0000
Bug 1599579 - Part 5: Ensure all views have matching BrowsingContextGroup IDs in getViews test, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D80258
cfdd8d5973d42e5dd82296b6126716d1aa89fe35: Bug 1599579 - Part 4: Expose BrowsingContextGroup.id to JS, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 30 Jun 2020 15:55:45 +0000 - rev 538048
Push 37557 by abutkovits@mozilla.com at Wed, 01 Jul 2020 03:27:11 +0000
Bug 1599579 - Part 4: Expose BrowsingContextGroup.id to JS, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D80257
73f6c956fc30b46959aa8d5401a8166d61e0fe5d: Bug 1599579 - Part 3: Load toplevel extension frames into a per-extension BrowsingContextGroup, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 30 Jun 2020 15:55:43 +0000 - rev 538047
Push 37557 by abutkovits@mozilla.com at Wed, 01 Jul 2020 03:27:11 +0000
Bug 1599579 - Part 3: Load toplevel extension frames into a per-extension BrowsingContextGroup, r=kmag This is done by tracking a specific BrowsingContextGroup ID on the WebExtensionPolicy in the parent process. Whenever a load is done with that policy, the browsing context is replaced to ensure it is loaded in the correct BrowsingContextGroup. This patch also ensures that extension iframes are always loaded in the same process as their embedder document, even if the frame was previously remote. Differential Revision: https://phabricator.services.mozilla.com/D80256
b4bdd8759433713a61d514918cbc1b5d35c771a0: Bug 1599579 - Part 1: Add the ability to specify a specific BrowsingContextGroup during process switch, r=kmag
Nika Layzell <nika@thelayzells.com> - Tue, 30 Jun 2020 16:52:53 +0000 - rev 538045
Push 37557 by abutkovits@mozilla.com at Wed, 01 Jul 2020 03:27:11 +0000
Bug 1599579 - Part 1: Add the ability to specify a specific BrowsingContextGroup during process switch, r=kmag Differential Revision: https://phabricator.services.mozilla.com/D80254
de04b387fa3b13c40b824f8de7d06b90b263d715: Bug 1647557 - Implement RemoteWebProgress using CanonicalBrowsingContext instead of MessageManager. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 30 Jun 2020 01:18:47 +0000 - rev 537893
Push 37555 by cbrindusan@mozilla.com at Tue, 30 Jun 2020 14:45:59 +0000
Bug 1647557 - Implement RemoteWebProgress using CanonicalBrowsingContext instead of MessageManager. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D70626
5338c655e022bf695557b3a3eee37641e03c1475: Bug 1649125 - Browsing context preservation should not ride the trains r=kmag
Paul Bone <pbone@mozilla.com> - Tue, 30 Jun 2020 01:10:54 +0000 - rev 537883
Push 37554 by nbeleuzu@mozilla.com at Tue, 30 Jun 2020 10:00:42 +0000
Bug 1649125 - Browsing context preservation should not ride the trains r=kmag Differential Revision: https://phabricator.services.mozilla.com/D81622
e82376ae2519850aad415741e1862124dd46d13a: Bug 1633379 - Part 2: Add support for in-process JSWindowActors, r=kmag,Yoric
Nika Layzell <nika@thelayzells.com> - Thu, 25 Jun 2020 20:35:18 +0000 - rev 537516
Push 37543 by abutkovits@mozilla.com at Fri, 26 Jun 2020 03:24:35 +0000
Bug 1633379 - Part 2: Add support for in-process JSWindowActors, r=kmag,Yoric This switches the `nsIContent{Parent,Child}` interface to be `nsIDOMProcess{Parent,Child}`, and also implements it on `InProcess{Parent,Child}`, along with the `ProcessActor` interface. Differential Revision: https://phabricator.services.mozilla.com/D80582
96ddb1b29a80f938b033724ae85781aa82c27ed5: Bug 1633379 - Part 1: Move PInProcess into dom/ipc, r=kmag,Yoric
Nika Layzell <nika@thelayzells.com> - Thu, 25 Jun 2020 17:50:51 +0000 - rev 537515
Push 37543 by abutkovits@mozilla.com at Fri, 26 Jun 2020 03:24:35 +0000
Bug 1633379 - Part 1: Move PInProcess into dom/ipc, r=kmag,Yoric This moves it near the cross-process `PContent` actor, and makes it more clear that this actor is only intended to be used for DOM things. Differential Revision: https://phabricator.services.mozilla.com/D80581
a26037f3225b5167f5431643a6a3d35ea4ad24ff: Bug 1633379 - Part 2: Add support for in-process JSWindowActors, r=kmag,Yoric
Nika Layzell <nika@thelayzells.com> - Thu, 25 Jun 2020 16:28:11 +0000 - rev 537438
Push 37542 by abutkovits@mozilla.com at Thu, 25 Jun 2020 21:45:10 +0000
Bug 1633379 - Part 2: Add support for in-process JSWindowActors, r=kmag,Yoric This switches the `nsIContent{Parent,Child}` interface to be `nsIDOMProcess{Parent,Child}`, and also implements it on `InProcess{Parent,Child}`, along with the `ProcessActor` interface. Differential Revision: https://phabricator.services.mozilla.com/D80582
efef0b59bcd814c0d94325f43a04909a86fd297b: Bug 1633379 - Part 1: Move PInProcess into dom/ipc, r=kmag,Yoric
Nika Layzell <nika@thelayzells.com> - Thu, 25 Jun 2020 15:49:15 +0000 - rev 537437
Push 37542 by abutkovits@mozilla.com at Thu, 25 Jun 2020 21:45:10 +0000
Bug 1633379 - Part 1: Move PInProcess into dom/ipc, r=kmag,Yoric This moves it near the cross-process `PContent` actor, and makes it more clear that this actor is only intended to be used for DOM things. Differential Revision: https://phabricator.services.mozilla.com/D80581
37fe053b2ed88872a73da09c2ea433f7eec98a87: Bug 1590762 - Part 1: Test that we don't double submit forms. r=kmag
Andreas Farre <farre@mozilla.com> - Tue, 23 Jun 2020 13:41:27 +0000 - rev 536909
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1590762 - Part 1: Test that we don't double submit forms. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D79145