These tests were timing out because `about:home` now runs in a different process.
Since these two tests aim to test something else (e.g. window leaks when
navigating between pages), we will redirect to a URL that loads in the same
process instead of `about:home` to avoid adding extra conditions for the
process flip.
See Bug 1336811 and Bug 1242643.
MozReview-Commit-ID: G0rhfA973R9
--HG--
extra : rebase_source : 158eb53174faa028edeebaf5970c123ba359a3e5
extra : intermediate-source : ebdca743668ce014c1cb9adfa00c1220256d357c
extra : source : a28443371b944ee00b1267dd5b9a22da6d28353b
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
--HG--
extra : rebase_source : a9a2aab3076a84b202176ca75bc9390315a5d5bf
extra : intermediate-source : f8a06d01437e3626189c60f1a87ff7038fb328ed
extra : source : 55c2a8d227dc91f965718aa09da9811cff0969a7
See next commit for more info. The idea is to use E10SUtils.canLoadURIInRemoteType to detect
if a URI can load in a given E10SUtils process type. Having it to accept a nsIXULRuntime
process type, which will be mapped back to an E10SUtils process type, is unnecessary.
MozReview-Commit-ID: KeYkuRDyqXO
--HG--
extra : rebase_source : c4f5d562657bc1ca0a2fe7c277f09add9c976975
extra : intermediate-source : b6996abc7d90edbc99d4ac0c5b9bb4a62c5ae5ae
extra : source : a8bba29ad2cb20239b87081f77cdf34249d3337b
Now that we have moved some about: pages to the privileged content process,
opening these URLs from a non-privileged content process will trigger SessionStore
to restore the tab state due to a process flip. We will set favicons for these
URLs earlier to avoid flickering and improve perceived performance.
This patch also prevents the spinner whenever a page with a local about: URI
(about:blank and about: pages that resolve to jar:// or file:// URIs) is
loaded from a process that the URI cannot load in (e.g. loading about:newtab
in the web content process), as well as during tab duplication or session
restoration for such local about: URIs.
Before this patch, there were additional frames when opening a new window, causing
browser/base/content/test/performance/browser_windowopen.js to fail. This patch
will reduce the number of frames when opening a new window.
MozReview-Commit-ID: yjj2964KSz
--HG--
extra : rebase_source : a5588b5b6496c983350f591602d0959f906235d5
extra : intermediate-source : 176f3ee14e67f493bafefbd599fbf0fe194a25a6
extra : source : cecc2d52e72e7c6e61137a9147735cb07a079d51
That variable, and the function that references it is only used by the openh264
code, so move it there.
Differential Revision: https://phabricator.services.mozilla.com/D9967
--HG--
extra : moz-landing-system : lando
Taskcluster knows where mozharness generates the logs, and can upload them from
there. Thus, mozharness no longer needs to copy the logs to a new directory.
Differential Revision: https://phabricator.services.mozilla.com/D9966
--HG--
extra : moz-landing-system : lando
