Bug 1472212 - Handle navigation away from privileged content process in RDM. r=jryans
Author: J. Ryan Stinnett <jryans@gmail.com>
Now that we are running about:home in the privileged content process, clicking
on a link in Activity Stream while having RDM activated will close the RDM
because a process flip will occur. This causes the following tests to time out
because the RDM has been deactivated:
- devtools/client/responsive.html/test/browser/browser_container_tab.js
- devtools/client/responsive.html/test/browser/browser_preloaded_newtab.js
This patch disables RDM in about:home and will load about:blank instead when
RDM is enabled.
MozReview-Commit-ID: D5EMyfkOM8l

Bug 1472212 - Handle navigation away from privileged content process in RDM. r=jryans
Author: J. Ryan Stinnett <jryans@gmail.com>
Now that we are running about:home in the privileged content process, clicking
on a link in Activity Stream while having RDM activated will close the RDM
because a process flip will occur. This causes the following tests to time out
because the RDM has been deactivated:
- devtools/client/responsive.html/test/browser/browser_container_tab.js
- devtools/client/responsive.html/test/browser/browser_preloaded_newtab.js
This patch disables RDM in about:home and will load about:blank instead when
RDM is enabled.
MozReview-Commit-ID: D5EMyfkOM8l

Bug 1472212 - Handle navigation away from privileged content process in RDM. r=jryans
Author: J. Ryan Stinnett <jryans@gmail.com>
Now that we are running about:home in the privileged content process, clicking
on a link in Activity Stream while having RDM activated will close the RDM
because a process flip will occur. This causes the following tests to time out
because the RDM has been deactivated:
- devtools/client/responsive.html/test/browser/browser_container_tab.js
- devtools/client/responsive.html/test/browser/browser_preloaded_newtab.js
This patch disables RDM in about:home and will load about:blank instead when
RDM is enabled.
MozReview-Commit-ID: D5EMyfkOM8l

Bug 1472212 - Handle navigation away from privileged content process in RDM. r=jryans
Author: J. Ryan Stinnett <jryans@gmail.com>
Now that we are running about:home in the privileged content process, clicking
on a link in Activity Stream while having RDM activated will close the RDM
because a process flip will occur. This causes the following tests to time out
because the RDM has been deactivated:
- devtools/client/responsive.html/test/browser/browser_container_tab.js
- devtools/client/responsive.html/test/browser/browser_preloaded_newtab.js
This patch disables RDM in about:home and will load about:blank instead when
RDM is enabled.
MozReview-Commit-ID: D5EMyfkOM8l

214a7d48d11a7f73502d2ba323058bdd13daebcd: bug 1485087 - remove the option to use the TLS session cache from nsITLSServerSocket r=jryans,mayhemer

bug 1485087 - remove the option to use the TLS session cache from nsITLSServerSocket r=jryans,mayhemer
As initially implemented, nsITLSServerSocket by default enabled the use of the
TLS session cache provided by NSS. However, no consumers of nsITLSServerSocket
actually used it. Because it was an option, though, PSM had to jump through some
hoops to a) make it work in the first place and b) not have NSS panic on
shutdown. Furthermore, it meant increased memory usage for every user of Firefox
(and again, nothing actually used the feature, so this was for naught).
In bug 1479918, we discovered that if PSM shut down before Necko, NSS could
attempt to acquire a lock on the session cache that had been deleted, causing a
shutdown hang. We probably should make it less easy to make this mistake in NSS,
but in the meantime bug 1479918 needs uplifting and this workaround is the
safest, most straight-forward way to achieve this.
Differential Revision: https://phabricator.services.mozilla.com/D3919

Bug 1479316: Pass through link related messages when in responsive design mode. r=jryans
Prior to bug 1453751 responsive design mode relied on the parent process seeing
that no favicon had been loaded and so defaulting to the root favicon for a
site. This would have meant that on some occasions responsive design mode didn't
show the correct favicon for pages that specified their own. This change passes
all the link related messages to the parent so favicons, feeds and searches
should work correctly.
Differential Revision: https://phabricator.services.mozilla.com/D3032

Bug 1479316: Pass through link related messages when in responsive design mode. r=jryans
Prior to bug 1453751 responsive design mode relied on the parent process seeing
that no favicon had been loaded and so defaulting to the root favicon for a
site. This would have meant that on some occasions responsive design mode didn't
show the correct favicon for pages that specified their own. This change passes
all the link related messages to the parent so favicons, feeds and searches
should work correctly.
Differential Revision: https://phabricator.services.mozilla.com/D2957

Bug 1444132 - Spawn a NetworkMonitorActor directly in the parent process. r=jryans
This allows to create NetworkEventActor directly from the parent process
and avoid most of the data being piped from the parent to the content processes.
MozReview-Commit-ID: 8p3A5yl5eVB

Bug 1444132 - Spawn a NetworkMonitorActor directly in the parent process. r=jryans
This allows to create NetworkEventActor directly from the parent process
and avoid most of the data being piped from the parent to the content processes.
MozReview-Commit-ID: 8p3A5yl5eVB

Bug 1477988 - Implements DebuggerServer.spawnActorInParentProcess. r=jryans
This new API allows to instanciate an actor in the parent process from actors running in the parent process.
The created actors are returned to the client from the actors running in content,
but after that, the client communicates directly with the created actors running in the parent process.
MozReview-Commit-ID: 5B3wRQ94UEx