Depends on D54657

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

--HG--
extra : moz-landing-system : lando

Fixes up ESR bouncer aliases now that ESR60 is EOL.
Adds check for latest products used by www.mozilla.org.
Enables the cron checks.
Fixes up a script error which meant we weren't checking all partial platforms in release automation.

Depends on D54656

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

Backed out changeset 82865b3cc6ed (bug 1599286) for Browser-chrome failures in content/minimal-xul.css. CLOSED TREE

Backed out changeset 7f9d6d996cb7 (bug 1599268) for WPT failures in /css/css-ui/caret-color-013.html

Lets Wayland sessions run vsync off wayland surface frame callbacks by creating
an interface for widgets to return a local VsyncSource, if applicable.

This interface is currently used for the compositor, and for refresh drivers
in the parent process. It is not yet used for vsync in content processes.

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

--HG--
extra : moz-landing-system : lando

Bug 1599304: Make SpecialPowers.Focus check for availability of this.manager.rootFrameLoader before dereferencing it. r=kmag

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

--HG--
extra : moz-landing-system : lando

Bug 1584723, skip browser_certViewer.js for tests run with 'verify' due to intermittent failures. r=keeler

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

DocumentChannel is enabled by default in nightly, but not beta.  We need to
enable it explicitly in the 2nd part of this test.

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

MessagePort::Dispatch(), for example, uses NS_DispatchToCurrentThread(), which
assumes nsThread.

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

Changes:

Some tests now pass when platform is updated from Ubuntu 16.04 to 18.04. They are annotated to restrict the failure expectation to version below Ubuntu 18.04, or expect passes for Ubuntu 18.04.

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

--HG--
extra : moz-landing-system : lando

Enables any type of document to use the special root element attributes
currently used by XUL <window>.

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

--HG--
extra : moz-landing-system : lando

Depends on D50917

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

--HG--
extra : moz-landing-system : lando

Bug 1496380 - include LSCopyDefaultApplicationURLForURL in recordreplay darwin process redirect, r=bhackett

Depends on D48742

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

--HG--
extra : moz-landing-system : lando

Bug 1496380 - stop recursion via the external protocol handler if Firefox is either the default OS handler or a configured external handler, r=mossop

This is an initial implementation of this idea that works on mac.
I've added a Windows implementation in another commit in this stack. I'll
look at a Linux one in a follow-up bug. I do not think we need them in the
child process implementation or on Android.

Effectively, this makes nsIHandlerInfo::LaunchWithURI() fall back to asking if
the handler info points to the OS default and that's us, or if it points to
a helper app and that's us. The latter is fairly easy to check, but the former,
more common case, is actually annoying - there don't seem to be APIs on the
external helper app service or the handler service that provide any information
about the app that's currently the default. So despite my belief that these
interfaces have too many methods that all do very similar things, and what we
need is fewer interfaces with fewer methods, I added another one...

For this mac implementation, I'm comparing bundle URLs and added newer API
usage for 10.10 and later to avoid deprecation warnings. I've not changed
the mac shell service as it uses bundle identifiers to check if we're the
default.

Another way of fixing these issues would be to complain about things when we
receive these URIs from external parties and our own config says that we will
just hand them to someone else. I decided not to do so because we end up with
at least one of the following problems:

- if we implement in BrowserContentHandler, that won't help for
  PWAs/Thunderbird
- if we try to implement in the external protocol handler, we'd need to start
  passing load flag information through to lots of checks.
- it wouldn't stop the recursion until we've already done one round of
  it for links that are in webpages, which seems suboptimal (ie, if you
  clicked a mailto: link on a webpage it'd go to the OS with that mailto link
  and only realize something's awry when we've gone back through the OS to us,
  rather than straightaway).

If we wanted to, we could add a fix like that in belt-and-suspenders fashion.

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

This patch centralizes the checking for discarded browsing contexts
for the media IPC messages. It also adds a check that the top BC is
not discarded, which seems to be causing crashes. A BC can be
non-discarded when its parent is discarded because discarding a BC
tree is not atomic.

This changes the BC we log the id of, but hopefully that is okay.

The patch also fixes the 'Browing' typo in the method name.

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

--HG--
extra : moz-landing-system : lando

Bug 1599372 - Integrate web-platform doc into https://firefox-source-docs.mozilla.org/ r=automatedtester

Depends on D54678

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

--HG--
extra : moz-landing-system : lando

Example:
https://searchfox.org/mozilla-central/rev/0678172d5b5c681061b904c776b668489e3355b0/testing/web-platform/tests/docs/index.md#62-71

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

--HG--
extra : moz-landing-system : lando

Changes:

For existing expected failures on Ubuntu 16.04, they are no different on Ubuntu 18.04. Include a new rule in the manifest to specify expected failures on Ubuntu 18.04.

This goes for both 32bit and 64bit versions of `web-platform-tests`.

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

--HG--
extra : moz-landing-system : lando

This commit updates our in-tree version of spec-tests to a recent bulk-memory
master (1e296604ae7c2aa2ce7619929a8817c9fd95941d) with one backport for our
addition of a bottom type. All the other backports and merges have been
dropped.

[1] https://github.com/eqrion/wasm-spec/commits/spidermonkey-tree-tests

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

--HG--
extra : moz-landing-system : lando

Bug 1598149 - Treat data/elem.drop as shrink-to-zero, disallow zero length past end of bounds. r=lth

Spec Issue: https://github.com/WebAssembly/bulk-memory-operations/issues/124

The inline path for memory.copy/fill are updated to fallback to the OOL path
when the length is 0 to have proper bounds checking behavior.

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

--HG--
extra : moz-landing-system : lando

Bulk memory reduces active segments to sequences of *.init that are executed
before the start function is called. This implies that an error here is to be
reported as a RuntimeError, as an error in the start function would. The latest
spec tests for bulk-memory check this, so we're required to update as well.

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

--HG--
extra : moz-landing-system : lando

Bug 1599286 - Prevent -moz-min-font-size-ratio from interfering with cached scrollbar styles. r=emilio

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

Bug 1598531 - Output Base Profiler logging to stderr, so it is correctly sync'd with MOZ_LOG - r=gregtatum

This is especially useful when debugging both Base Profiler and Gecko Profiler,
so that their messages are correctly sequenced.

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

In practice the previous test that was deleting Base Profiler data when the
index became greater that 1 was correct for Firefox, because the Base Profiler
*always* starts before the very first Gecko Profiler active instance.

However in tests (like the one in the following patch) this may not be true,
because each test may start and stop the profiler, and the recent storage update
means that the index doesn't go back to 1. So when a test (apart from the first
test to use the profiler) attemps to use the Base Profiler, that Base Profiler
data will be immediately discarded because the index is already greater than 1
(from previous tests).

This change is more future-proof as well, in case we later want to use the Base
Profiler more than once in a Firefox instance.

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

--HG--
extra : moz-landing-system : lando

Bug 1598992 - Use same thread names in Base Profiler filter as in Gecko, and suffix with "(pre-xul)" in JSON - r=gregtatum

The Base Profiler originally named the main thread "Main Thread", which is
friendlier than "GeckoMain". However this makes it more difficult to combine the
controls for both profilers if they use different names.

So now both profilers use "GeckoMain", so filters can be exactly the same.
Base Profiler adds "(pre-xul)" to the name to distinguish tracks in the
frontend -- This distinction is actually necessary so the frontend doesn't get
confused by threads with the exact same name, but eventually tracks will get
combined in the frontend as well.

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

--HG--
extra : moz-landing-system : lando

This ensures that no more Base Profiler (BP) activity can happen when Gecko
Profiler (GP) starts.
In particular on Linux this is needed because the BP sampler sends signals to
stop threads, and the just-starting GP could receive this signal before it is
fully ready to handle it with its own sampler.

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

--HG--
extra : moz-landing-system : lando

JSON profiles from the Base Profiler were assumed to be empty if they contained
zero characters, but in fact they contain one character (a single newline).

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando