Граф коммитов

66 Коммитов

Автор SHA1 Сообщение Дата
Hiroyuki Ikezoe 8aa17d97ef Bug 1553012 - Make PresShell::ScrollFrameRectIntoView work in fission world. r=mattwoodrow,nika,tnikkel
Differential Revision: https://phabricator.services.mozilla.com/D36136

--HG--
extra : moz-landing-system : lando
2019-07-09 05:34:27 +00:00
Henri Sivonen 381b9f24a9 Bug 1562796 - Pop BrowserParents of the previous window when raising/creating a window. r=m_kato
Differential Revision: https://phabricator.services.mozilla.com/D36581

--HG--
extra : moz-landing-system : lando
2019-07-03 06:06:26 +00:00
Henri Sivonen 91cd6a0d25 Bug 1549930 - Avoid popping BrowserParent in response to window lowering. r=masayuki
Differential Revision: https://phabricator.services.mozilla.com/D30873

--HG--
extra : moz-landing-system : lando
2019-06-14 07:02:18 +00:00
Barret Rennie 43bd779652 Bug 1510569 - Port Content:LoadURIResult message to IPDL r=mconley
The `WebProgress#sendLoadCallResult` method only existed to send a empty async
message and was only called from the `WebNavigationChild`. Since
`WebNavigationChild` is in the process of being removed, it makes sense to
inline the replaced method into its call site.

Differential Revision: https://phabricator.services.mozilla.com/D34566

--HG--
extra : moz-landing-system : lando
2019-06-13 21:00:34 +00:00
Barret Rennie 2de25cc4ca Bug 1510569 - Port onLocationChange notifications inside WebProgressChild.jsm to C++ r=Ehsan
Differential Revision: https://phabricator.services.mozilla.com/D34563

--HG--
extra : moz-landing-system : lando
2019-06-13 21:08:40 +00:00
Barret Rennie 5ac437d877 Bug 1510569 - Correctly reconstruct nsIRequest in tab parent r=Ehsan
When `TabParent::ReconstructWebProgressRequest` was introduced in
31b206e2046f63af31424489e3d61d7761805878, it mistakenly was unconditionally
constructing an `nsIRequest` from the received `RequestData`, even when the URI
was null.

Additionally `ReconstructWebProgressRequest` has been updated to use the Gecko
style for out parameters (accepting an `nsIFoo**` and passing
`getter_AddRefs(...)` instead of `nsCOMPtr<nsIFoo>&`).

Differential Revision: https://phabricator.services.mozilla.com/D34445

--HG--
extra : moz-landing-system : lando
2019-06-13 20:59:35 +00:00
Narcis Beleuzu ed60adfc3c Backed out 5 changesets (bug 1510569) for bustages on BrowserChild.cpp . CLOSED TREE
Backed out changeset 4f0f5351be8b (bug 1510569)
Backed out changeset 14bbe0916bdd (bug 1510569)
Backed out changeset 19e734aeffa9 (bug 1510569)
Backed out changeset abb51690fd32 (bug 1510569)
Backed out changeset 1bf1907ee0c9 (bug 1510569)
2019-06-13 22:08:23 +03:00
Barret Rennie 75f83f43fc Bug 1510569 - Port Content:LoadURIResult message to IPDL r=mconley
The `WebProgress#sendLoadCallResult` method only existed to send a empty async
message and was only called from the `WebNavigationChild`. Since
`WebNavigationChild` is in the process of being removed, it makes sense to
inline the replaced method into its call site.

Differential Revision: https://phabricator.services.mozilla.com/D34566

--HG--
extra : moz-landing-system : lando
2019-06-13 17:55:04 +00:00
Barret Rennie 15c17bbb9f Bug 1510569 - Port onLocationChange notifications inside WebProgressChild.jsm to C++ r=Ehsan
Differential Revision: https://phabricator.services.mozilla.com/D34563

--HG--
extra : moz-landing-system : lando
2019-06-13 17:54:23 +00:00
Barret Rennie 3630abbeca Bug 1510569 - Correctly reconstruct nsIRequest in tab parent r=Ehsan
When `TabParent::ReconstructWebProgressRequest` was introduced in
31b206e2046f63af31424489e3d61d7761805878, it mistakenly was unconditionally
constructing an `nsIRequest` from the received `RequestData`, even when the URI
was null.

Additionally `ReconstructWebProgressRequest` has been updated to use the Gecko
style for out parameters (accepting an `nsIFoo**` and passing
`getter_AddRefs(...)` instead of `nsCOMPtr<nsIFoo>&`).

Differential Revision: https://phabricator.services.mozilla.com/D34445

--HG--
extra : moz-landing-system : lando
2019-06-13 17:54:10 +00:00
Andrew McCreight 1f5eaf0169 Bug 1557808 - Call BrowserParent::SendSkipBrowsingContextDetach in SendSkipBrowsingContextDetach. r=nika
The nsFrameLoader for the BrowserParent is always the toplevel
<xul:browser>'s, but we actaully want to skip the detach for the
browsing context for the current browser child.

Differential Revision: https://phabricator.services.mozilla.com/D34237

--HG--
extra : moz-landing-system : lando
2019-06-10 15:13:24 +00:00
Nika Layzell b5b7f6b728 Bug 1451455 - Fire the 'load' event on out-of-process iframes, r=rhunt
This is done by sending a message over PBrowser and PBrowserBridge when the
event would fire to fire it in the correct process.

Differential Revision: https://phabricator.services.mozilla.com/D33083

--HG--
extra : moz-landing-system : lando
2019-06-06 14:57:17 +00:00
Ryan Hunt 67035334dd Bug 1556555 - Generate TabId for PBrowserBridge in content process and retain reference to it. r=nika
This lets us get the TabId for the PBrowser created via PBrowserBridge in the embedding process.

Differential Revision: https://phabricator.services.mozilla.com/D33565

--HG--
extra : rebase_source : 32f4b465426e4d19e4a81df0fc67076b0132038b
extra : source : 5e938107e10ed489477d104c70e413e0c4e6091d
extra : histedit_source : 24bda5ef39697eb4ba9e691d4a3afcc5f144737b
2019-06-02 13:42:03 -04:00
Ryan Hunt 3fb2657eb6 Bug 1556548 - Rename RenderFrame to RemoteLayerTreeOwner. r=mattwoodrow
RenderFrame is a very poor name for what this class does. RemoteLayerTreeOwner
isn't perfect (it's not the only thing that owns layer trees), but it's
hopefully clearer.

Differential Revision: https://phabricator.services.mozilla.com/D33564

--HG--
rename : layout/ipc/RenderFrame.cpp => layout/ipc/RemoteLayerTreeOwner.cpp
rename : layout/ipc/RenderFrame.h => layout/ipc/RemoteLayerTreeOwner.h
extra : rebase_source : 890e54b93f5979a2430c35028110aa7f2091c550
extra : source : f50dd4cde03beb99ed27397e06f81748ae87b727
extra : histedit_source : 2d7eed25156829b2502f1712880df962a781adcf
2019-06-02 13:51:33 -04:00
Ryan Hunt 298a301151 Bug 1556548 - Make RenderFrame an internal detail to BrowserParent. r=mattwoodrow,farre
Code outside of BrowserParent should just get the LayersId from a getter
and not worry about RenderFrame.

Differential Revision: https://phabricator.services.mozilla.com/D33562

--HG--
extra : rebase_source : 63f9f9680a7cb16a18d9e56999e02a124aa63429
extra : source : e86839ca63260b09184755c98890fa8abf371530
extra : histedit_source : 34333f5f78ecf9b4f3e12c6175a6e81724a41fb2
2019-05-31 16:00:57 -05:00
Jim Porter f665b313f3 Bug 1552017 - Expand the kinds of URLs that can cancel content JS when navigating; r=smaug
This patch makes several changes to the kinds of URLs where we can cancel
content JS when navigating between them:

 1) When navigating directly to a URL (e.g. by typing something into the
    location bar and hitting Enter), we allow canceling content JS if the URLs
    differ in any way *except* their ref ("#"). To help with this, we also
    attempt to fix up the URL (e.g. by prepending "http://" to it).

 2) When navigating through history, we allow canceling content JS if the
    `prePath` part of the URLs differ. Most notably, this allows canceling
    content JS when one of the URLs is an `about:` page (e.g. when hitting the
    Home button).

 3) We explicitly disallow cancelling content JS if the currently-running JS
    is trusted or if the page being navigated away from is anything but
    http(s): or file:.

 4) We also disallow cancelling content JS for windows that are still being
    created (e.g. when creating a new tab or window via `window.open`). For
    more background on this, see the comments about `mCreatingWindow` in
    dom/ipc/BrowserParent.h.

 5) We ensure that, when attempting to cancel JS, the tab ID of the
    currently-running script matches the original tab that requested the
    cancellation. This avoids a race condition in which a particular JSContext
    has already moved on to executing another tab's JS by the time we hit our
    interrupt callback.

Differential Revision: https://phabricator.services.mozilla.com/D31875

--HG--
extra : moz-landing-system : lando
2019-06-04 16:19:27 +00:00
James Teh 86e3c8af49 Bug 1543313 part 1: Allow identification and retrieval of DocAccessibleParents at the top level of their content process. r=eeejay
DocAccessibleParent already has IsTopLevel(), which identifies a document at the top level of the hierarchy; i.e. it has no parents.
Now that we have out-of-process iframes, we need to be able to identify and retrieve documents at the top level of their content process, even if they are embedded by another remote document.
DocAccessibleParent::IsTopLevelInContentProcess() has been introduced to achieve this.
BrowserParent::GetTopLevelDocAccessible() now uses this instead of IsTopLevel(), since we want to be able to get the top DocAccessibleParent even for a BrowserParent for an out-of-process iframe.

Differential Revision: https://phabricator.services.mozilla.com/D32282

--HG--
extra : moz-landing-system : lando
2019-05-31 03:27:26 +00:00
Coroiu Cristina d075308d70 Backed out changeset 86e87b18a282 (bug 1451455) for mochitest failures at dom/html/test/test_ignoreuserfocus.html on a CLOSED TREE 2019-06-04 01:23:12 +03:00
Nika Layzell f4d3fdbcdd Bug 1451455 - Fire the 'load' event on out-of-process iframes, r=rhunt
This is done by sending a message over PBrowser and PBrowserBridge when the
event would fire to fire it in the correct process.

Differential Revision: https://phabricator.services.mozilla.com/D33083

--HG--
extra : moz-landing-system : lando
2019-06-03 20:03:37 +00:00
Neil Deakin dcfccf267d Bug 1443683, support drag and drop in out of process frames; this is done by storing the drag information about the data to be dragged and visualization image in the event state manager instead of the BrowserParent and passing this information on to the drag service, r=nika
--HG--
extra : rebase_source : 0ccb645d652b064e647d5693aaf480d7066e6fdf
2019-05-14 11:04:38 -04:00
shindli 7b0d34e0a4 Backed out changeset 79436da3bf79 (bug 1549930) for causing perma browser chrome failures in browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about.js CLOSED TREE 2019-05-27 18:09:53 +03:00
Henri Sivonen b5386fef86 Bug 1549930 - Avoid popping BrowserParent in response to window lowering. r=masayuki
Differential Revision: https://phabricator.services.mozilla.com/D30873

--HG--
extra : moz-landing-system : lando
2019-05-27 12:22:37 +00:00
Liang-Heng Chen aea7247098 Bug 1330467 - part 8. Make canvas permission respect FPI; r=johannh,jrmuizel
Differential Revision: https://phabricator.services.mozilla.com/D19929

--HG--
extra : moz-landing-system : lando
2019-05-17 13:23:04 +00:00
Barret Rennie 1cca2811c0 Bug 1510569 - Port onStateChange notifications inside WebProgressChild.jsm to C++ r=baku,kmag
We now also only access the document when the state is
nsIWebProgress::STATE_STOP. The comments in the previous code indicated that
touching the document inside the event handler when the state is not STATE_STOP
would result in the content creating a new about:blank document to retrieve the
values from. However, it then went on to do this in another location, causing a
document to be created whenever we received an onStateChange event. This should
no longer occur.

Differential Revision: https://phabricator.services.mozilla.com/D28125

--HG--
extra : moz-landing-system : lando
2019-05-23 18:49:08 +00:00
Barret Rennie bda47d9434 Bug 1510569 - Refactor BrowserParent nsIWebProgress handlers r=kmag
The BrowserParent's IPC receive methods for nsIWebProgress events in the
BrowserChild were all doing the same set up to ensure they had the correct
state to process them. This has now been refactored out into a single method.

Differential Revision: https://phabricator.services.mozilla.com/D30730

--HG--
extra : moz-landing-system : lando
2019-05-24 15:45:05 +00:00
Ryan Hunt 9078c825ec Bug 1525720, part 14 - Move final bits of nsIRemoteTab implementation to BrowserHost. r=nika
This commit moves the actual implementation of nsIRemoteTab from BrowserParent
to BrowserHost, without any functional changes.

Differential Revision: https://phabricator.services.mozilla.com/D31445

--HG--
extra : source : d25963c72ff7981990660050182a82ea3e935f53
2019-05-08 15:47:18 -05:00
Ryan Hunt 4683a8b07a Bug 1525720, part 13 - Stop inheriting nsIRemoteTab interface in BrowserParent. r=nika
This commit removes nsIRemoteTab as a parent class from BrowserParent,
so that BrowserHost is the only concrete implementation of nsIRemoteTab.

Some static_cast's are updated to cast to BrowserHost, and other places
have to be updated to pass a BrowserHost instead of a BrowserParent.

WindowGlobalParent had a getter to return it's managing BrowserParent
as a nsIRemoteTab. I couldn't find a use of this in-tree, so I've just
opt-ed to remove it. If there's a use-case, we can add something back
in.

Differential Revision: https://phabricator.services.mozilla.com/D31444

--HG--
extra : source : 810b7371987139844429d0206f9da6a7701a1efc
2019-05-08 14:34:47 -05:00
Ryan Hunt fd25ba1f84 Bug 1525720, part 10 - Link BrowserParent and BrowserHost on creation. r=nika
This commit adds a link from BrowserParent to it's owning BrowserHost
if it is the root BrowserParent.

Differential Revision: https://phabricator.services.mozilla.com/D31441

--HG--
extra : source : d3b2ac8d5ca4bd350603085c3cb9f6a51269e075
2019-05-15 10:34:03 -05:00
Ryan Hunt cadf33a327 Bug 1525720, part 2 - Move UITabResolutionChanged method to nsIRemoteTab interface from BrowserParent. r=smaug
This reduces the amount of code that assumes that BrowserParent implements nsIRemoteTab.

Differential Revision: https://phabricator.services.mozilla.com/D31430

--HG--
extra : source : 5f1c1b609ec1ecc28734e1b6daeeb3f6854ded38
2019-04-24 23:05:40 -05:00
Ryan Hunt ce59f54daf Bug 1525720, part 1 - Allow calling BrowserParent::InitRendering multiple times, and remove RenderFrame dependency from nsFrameLoader. r=kats
This cleanup will simplify refactoring nsFrameLoader later.

Differential Revision: https://phabricator.services.mozilla.com/D31429

--HG--
extra : source : 00d83f1d02e015735d580045524eceeeccdc4e28
2019-04-24 22:36:27 -05:00
Gurzau Raul 57f573a6ff Backed out 18 changesets (bug 1525720) for mass failures on Windows platform e.g ProcessPriorityManager.cpp on a CLOSED TREE.
Backed out changeset 1f2e86c2d691 (bug 1525720)
Backed out changeset 9b79caa460a0 (bug 1525720)
Backed out changeset e65cb2d4c5a5 (bug 1525720)
Backed out changeset 99f971a02d87 (bug 1525720)
Backed out changeset d25963c72ff7 (bug 1525720)
Backed out changeset 810b73719871 (bug 1525720)
Backed out changeset ee10a8254481 (bug 1525720)
Backed out changeset 1bcf9f586c55 (bug 1525720)
Backed out changeset d3b2ac8d5ca4 (bug 1525720)
Backed out changeset 697774dd8984 (bug 1525720)
Backed out changeset eadeacbe4483 (bug 1525720)
Backed out changeset 32eeee79d628 (bug 1525720)
Backed out changeset 07678a2fa9e7 (bug 1525720)
Backed out changeset 757b4f595cc4 (bug 1525720)
Backed out changeset b255e0a84e12 (bug 1525720)
Backed out changeset 9a255864f75d (bug 1525720)
Backed out changeset 5f1c1b609ec1 (bug 1525720)
Backed out changeset 00d83f1d02e0 (bug 1525720)
2019-05-23 01:57:16 +03:00
Ryan Hunt 9b1bbaea5b Bug 1525720, part 14 - Move final bits of nsIRemoteTab implementation to BrowserHost. r=nika
This commit moves the actual implementation of nsIRemoteTab from BrowserParent
to BrowserHost, without any functional changes.

Differential Revision: https://phabricator.services.mozilla.com/D31445

--HG--
extra : rebase_source : 2e6533dfa69a3278300eb70d5258bcd0a3aba68b
extra : histedit_source : a26ba68b78eb6d16cdffbc630f4410c5dd46a367
2019-05-08 15:47:18 -05:00
Ryan Hunt 93d6ab4ec4 Bug 1525720, part 13 - Stop inheriting nsIRemoteTab interface in BrowserParent. r=nika
This commit removes nsIRemoteTab as a parent class from BrowserParent,
so that BrowserHost is the only concrete implementation of nsIRemoteTab.

Some static_cast's are updated to cast to BrowserHost, and other places
have to be updated to pass a BrowserHost instead of a BrowserParent.

WindowGlobalParent had a getter to return it's managing BrowserParent
as a nsIRemoteTab. I couldn't find a use of this in-tree, so I've just
opt-ed to remove it. If there's a use-case, we can add something back
in.

Differential Revision: https://phabricator.services.mozilla.com/D31444

--HG--
extra : rebase_source : 63070e3c2b90c9134f9106028e124935c8dad009
extra : histedit_source : 807f2ff684d86008077be07b0894f39a925fe778
2019-05-08 14:34:47 -05:00
Ryan Hunt ad5807c04e Bug 1525720, part 10 - Link BrowserParent and BrowserHost on creation. r=nika
This commit adds a link from BrowserParent to it's owning BrowserHost
if it is the root BrowserParent.

Differential Revision: https://phabricator.services.mozilla.com/D31441

--HG--
extra : rebase_source : 8cb8fa816198fd2bf660f092227e92e69bc63c97
extra : histedit_source : 1597cb06d341ec87c27c67a1b8aa858fe0bfe8bc
2019-05-15 10:34:03 -05:00
Ryan Hunt e084a16216 Bug 1525720, part 2 - Move UITabResolutionChanged method to nsIRemoteTab interface from BrowserParent. r=smaug
This reduces the amount of code that assumes that BrowserParent implements nsIRemoteTab.

Differential Revision: https://phabricator.services.mozilla.com/D31430

--HG--
extra : rebase_source : d639864ba86001cf90a8b3d42b6eda97a7f829ac
extra : histedit_source : 6f6f1e0b6d3561e478391ce9e72a8a2dbc280983
2019-04-24 23:05:40 -05:00
Ryan Hunt b3a1c0edb7 Bug 1525720, part 1 - Allow calling BrowserParent::InitRendering multiple times, and remove RenderFrame dependency from nsFrameLoader. r=kats
This cleanup will simplify refactoring nsFrameLoader later.

Differential Revision: https://phabricator.services.mozilla.com/D31429

--HG--
extra : rebase_source : 416d91a0119c4df11faf73076fb425bb0471a48e
extra : histedit_source : 62cc6bc346b2b961860b3e070fd34ca69b9cf0e0
2019-04-24 22:36:27 -05:00
Alphan Chen 2dbd18c6c8 Bug 1549973 - Force tabState flush from C++ listener before tab is closed r=peterv
Differential Revision: https://phabricator.services.mozilla.com/D30475

--HG--
extra : moz-landing-system : lando
2019-05-22 09:06:14 +00:00
Noemi Erli cc1f5b44f2 Backed out 4 changesets (bug 1510569) for mass test failures CLOSED TREE
Backed out changeset c5488e2770a6 (bug 1510569)
Backed out changeset df98eef1f640 (bug 1510569)
Backed out changeset db6da7f94a92 (bug 1510569)
Backed out changeset fb696b92c13d (bug 1510569)
2019-05-21 23:41:41 +03:00
Emilio Cobos Álvarez 4cd1208da9 Bug 416771 - Use RefPtr<Element> rather than nsCOMPtr in BrowserParent. r=NeilDeakin
Depends on D31641

Differential Revision: https://phabricator.services.mozilla.com/D31642

--HG--
extra : moz-landing-system : lando
2019-05-21 14:14:57 +00:00
Barret Rennie 461c1d28b9 Bug 1510569 - Port onStateChange notifications inside WebProgressChild.jsm to C++ r=baku,kmag
We now also only access the document when the state is
nsIWebProgress::STATE_STOP. The comments in the previous code indicated that
touching the document inside the event handler when the state is not STATE_STOP
would result in the content creating a new about:blank document to retrieve the
values from. However, it then went on to do this in another location, causing a
document to be created whenever we received an onStateChange event. This should
no longer occur.

Differential Revision: https://phabricator.services.mozilla.com/D28125

--HG--
extra : moz-landing-system : lando
2019-05-21 19:28:52 +00:00
Barret Rennie 8dc24e1342 Bug 1510569 - Refactor BrowserParent nsIWebProgress handlers r=kmag
The BrowserParent's IPC receive methods for nsIWebProgress events in the
BrowserChild were all doing the same set up to ensure they had the correct
state to process them. This has now been refactored out into a single method.

Differential Revision: https://phabricator.services.mozilla.com/D30730

--HG--
extra : moz-landing-system : lando
2019-05-21 19:28:19 +00:00
Cosmin Sabou e565aa827a Backed out 4 changesets (bug 1510569) for causing build bustages on nsIDocShell.idl CLOSED TREE
Backed out changeset 57f49df057be (bug 1510569)
Backed out changeset de97a258fcfd (bug 1510569)
Backed out changeset 4b0ed20ab3bc (bug 1510569)
Backed out changeset 1d8ab383d3e9 (bug 1510569)
2019-05-21 20:30:01 +03:00
Barret Rennie 748556eba1 Bug 1510569 - Port onStateChange notifications inside WebProgressChild.jsm to C++ r=baku,kmag
We now also only access the document when the state is
nsIWebProgress::STATE_STOP. The comments in the previous code indicated that
touching the document inside the event handler when the state is not STATE_STOP
would result in the content creating a new about:blank document to retrieve the
values from. However, it then went on to do this in another location, causing a
document to be created whenever we received an onStateChange event. This should
no longer occur.

Differential Revision: https://phabricator.services.mozilla.com/D28125

--HG--
extra : moz-landing-system : lando
2019-05-21 17:09:14 +00:00
Barret Rennie 50f9f3dd7a Bug 1510569 - Refactor BrowserParent nsIWebProgress handlers r=kmag
The BrowserParent's IPC receive methods for nsIWebProgress events in the
BrowserChild were all doing the same set up to ensure they had the correct
state to process them. This has now been refactored out into a single method.

Differential Revision: https://phabricator.services.mozilla.com/D30730

--HG--
extra : moz-landing-system : lando
2019-05-21 17:08:42 +00:00
Mihai Alexandru Michis 97df17e745 Backed out 11 changesets (bug 1330467) as requested by xeonchen on IRC. CLOSED TREE
Backed out changeset 0229d5353d50 (bug 1330467)
Backed out changeset 2f2308fe5747 (bug 1330467)
Backed out changeset 2cd09bae2bdf (bug 1330467)
Backed out changeset 2648f5bb1804 (bug 1330467)
Backed out changeset 4686eebd8962 (bug 1330467)
Backed out changeset b43fa07d5756 (bug 1330467)
Backed out changeset 35d96a4ff659 (bug 1330467)
Backed out changeset 6ac44130d2bb (bug 1330467)
Backed out changeset f939c61e051f (bug 1330467)
Backed out changeset 0ae215d91758 (bug 1330467)
Backed out changeset 1d48bdbb4035 (bug 1330467)
2019-05-17 16:19:06 +03:00
Kyle Machulis 9f9436d028 Bug 1540839 - Add ability to preserve browsing contexts between FrameLoaders; r=nika
When changing processes and therefore destroying/rebuilding
frameloaders, add ability to keep the browsing context around and add
it to the new frameloader.

Differential Revision: https://phabricator.services.mozilla.com/D26267
2019-05-14 10:51:04 -07:00
Razvan Maries 1be8bab7d1 Backed out 8 changesets (bug 1540839) for build bustages. CLOSED TREE
Backed out changeset f7e477858ab7 (bug 1540839)
Backed out changeset 55e841a0f005 (bug 1540839)
Backed out changeset b71b58e40426 (bug 1540839)
Backed out changeset 484a54613358 (bug 1540839)
Backed out changeset b34c4d71f202 (bug 1540839)
Backed out changeset 8ff2ff524489 (bug 1540839)
Backed out changeset 27492a30286c (bug 1540839)
Backed out changeset f1c35e8e84f6 (bug 1540839)
2019-05-14 04:23:27 +03:00
Kyle Machulis deebf851e0 Bug 1540839 - Add ability to preserve browsing contexts between FrameLoaders; r=nika
When changing processes and therefore destroying/rebuilding
frameloaders, add ability to keep the browsing context around and add
it to the new frameloader.

Differential Revision: https://phabricator.services.mozilla.com/D26267
2019-05-13 17:58:44 -07:00
Liang-Heng Chen 284baaf7d8 Bug 1330467 - part 8. Make canvas permission respect FPI; r=johannh,jrmuizel
Differential Revision: https://phabricator.services.mozilla.com/D19929

--HG--
extra : moz-landing-system : lando
2019-05-07 22:19:02 +00:00
Ryan Hunt 7df4ba7bbf Bug 1549753 - Add Visit methods for visiting the tree of BrowserParent and BrowserBridgeParent. r=afarre
Differential Revision: https://phabricator.services.mozilla.com/D30215

--HG--
extra : rebase_source : f885c62dc8a24974d67b2c65e19ab42576e8640e
extra : histedit_source : f884a8ed29c99bd0e71f78d6adaf61a9f19ce21e
2019-05-07 11:08:22 -05:00