Nika Layzell 6eb2084136 Bug 1544811 - Use web processes on a per-site basis for fission-enabled windows, r=mconley ... This patch introduces a new type of content process, which has a dynamic name. This type of content process is labeled as `webIsolated=${SITE_ORIGIN}` and is used within fission-enabled windows. To enable this, additional information about the fission status of the target window must be passed into E10SUtils. This was done by updating every call site manually to pass an extra boolean. A better solution perhaps should be used in the future. With this patch enabled, we now perform process switches, but only when navigating to HTTP URIs. If we navigate to a non-HTTP URI in an iframe with fission enabled, it will not behave correctly. This must be done in a follow-up. Differential Revision: https://phabricator.services.mozilla.com/D29570 --HG-- extra : moz-landing-system : lando		2019-05-03 21:31:57 +00:00
..
307redirect.sjs
browser.ini	Bug 1539163 - Part 3: tests for switch processes, r=qdot	2019-04-17 00:53:34 +00:00
browser_httpCrossOriginOpenerPolicy.js
browser_httpResponseProcessSelection.js
browser_httpToFileHistory.js
browser_oopProcessSwap.js	Bug 1544811 - Use web processes on a per-site basis for fission-enabled windows, r=mconley	2019-05-03 21:31:57 +00:00
browser_RemoteWebNavigation.js
coop_header.sjs
dummy_page.html
file_postmsg_parent.html	Bug 1539163 - Part 3: tests for switch processes, r=qdot	2019-04-17 00:53:34 +00:00
head.js
print_postdata.sjs