Also upgrade eslint and eslint-plugin-react whilst we're here.

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

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

Right now, pushed streams don't get put in the priority hierarchy
anyway, and with the code as it was, we were sending an illegal PRIORITY
frame for stream 0. This prevents that from happening. We should
probably think about putting pushed streams in the priority hierarchy at
some point.

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

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

Bug 1398718 - change default pref to on for lowercase header names in XHR.getAllResponseHeaders; r=hsivonen

change default pref to on for lowercase header names in XHR.getAllResponseHeaders

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

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

Bug 1493310: Add a way to access certain functionality of nsXREDirProvider for testing purposes. r=froydnj

In order to be able to have even basic xpcshell tests for bug 1474285 I need
nsXREDirProvider to be accessible and to be able to override a couple of the
directories it returns.

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

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

Add the first version of the IPDL-JS API, which allow chrome JS to load IPDL files and use them to communicate accross Content processes.
See IPDLProtocol.h for more information regarding how to use the API.

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

--HG--
rename : ipc/moz.build => ipc/ipdl_new/moz.build
extra : moz-landing-system : lando

--HG--
rename : taskcluster/ci/cron-bouncer-check/kind.yml => taskcluster/ci/bouncer-check/kind.yml

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

--HG--
rename : taskcluster/ci/bouncer-check/kind.yml => taskcluster/ci/cron-bouncer-check/kind.yml
extra : moz-landing-system : lando

Backed out changeset 628ebca30ce3 (bug 1490240) for bustages on [Unified_cpp_crashreporter0.obj]. CLOSED TREE

Buildbot had a feature where a notification email would be sent to
the user who triggered the build jobs once Buildbot had begun
processing the request. Since we have migrated off Buildbot, we
have lost this much-appreciated functionality. Taskcluster
allows us to send emails when a task fails, raises an exception
or completes successfully. We already send notification emails
out for the first two cases, sending an email on completion of
the Gecko decision task would essentially replicate the Buildbot
functionality. This commit adds the "on-completed" notification
route when the repository project alias corresponds to a known
try repo. In that case, we also add data to the
`extra.notification.email` section which creates a link to the
Treeherder view for the scheduled jobs.

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

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

Bug 1492114 - Really ensure that the Third-Party Cookies description doesn't wrap unnecessarily r=johannh

The selector should apply to deck elements that do have a selectedIndex
attribute but it's not 0.

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

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

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

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

Depends on D6609

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

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

Depends on D6608

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

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

Depends on D6607

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

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

Depends on D6606

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

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

Depends on D6605

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

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

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

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

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

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

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

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

Bug 1492759 - Use the principal stored in CompartmentOriginInfo instead of JS_GetCompartmentPrincipals for Xray expandos. r=bholley

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

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

Backed out changeset 6f81edbb4e87 (bug 1493549) for wpt failures on /mediacapture-image/ImageCapture-creation.https.html. CLOSED TREE

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

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

This patch makes the parser-worker available at the toolbox level.
This way, the console does not have to rely on the debugger being
open to map top-level await expression.
In order to make the worker works in the toolbox, some changes
are required (passing a window object, checking inToolbox differently).

We take this as an opportunity to *not* display the async iife result,
a promise, in the console. This is made by checking if the input was
mapped, and if so, ignoring the result we get from the server.

A couple tests are added to ensure the basic usage works as expected.

This patch should be considered as a v0 for top-level await evaluation
as there are things that are not perfect here. Since we rely on console.log
the result are treated differently from other evaluation results:
- the style is different
- the result gets added to the log cache (when restarting the console,
the results will still be displayed, but not the commands).
- the results can be filtered, although evaluation results should not
- `$_` after a top-level await evaluation returns the Promise created
by the async iife, not the result that was displayed in the console.

All those should be addressed in Bug 1410820.

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

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

convert uses of "defer" to "new Promise" in client/shadereditor

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

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

Saving and filling the countries via Form Autofill will still be limited to certain countries
but this allows the storage to be useful for Web Payments in other countries.

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

--HG--
extra : amend_source : c6810478b747cf51aaaafa73f83682cb23711231

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

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

MozReview-Commit-ID: C6ehO1TG5YO

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

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

The code does check for the case where a container has no children.
However, before it does so, it tries to check whether it needs to skip a text leaf child.
This check previously assumed there was a child to check, which crashed for a container with no children.

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

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

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

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

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

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

This cherry-picks servo/servo#21789.

This reverts the relevant bits from #21746 so that style and dependencies can
build with stable.

This is important because:

 * `selectors` is a published crate.

 * Gecko compiles with stable (more or less).

I reviewed that PR under the assumption that the union feature was stable, since
untagged unions are stable since 1.19, but turns out that smallvec uses non-Copy
types in unions, which are still unstable.

This leaves the union feature used on Servo, so that it gets testing, taking
advantage of features being additive.

This cherry-picks servo/servo#21788.

We had a mix of 0.6.2 and 0.6.5 (which is the current release),
this unifies to the latest version. It also enables the union
feature which removes the discriminant, reducing memory usage.

This cherry-picks servo/servo#21746.

Enable a disabled addon when user re-installs the same version.

Before this change disabled addons couldn't be enabled back even if user intentionally reinstalls the same version of addon.
Now if user reinstalls the same version - addon will be enabled back.

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

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

Bug 1338158: use 'unset' value more in UA stylesheets, in cases where we're already just resetting the property. r=dholbert

--HG--
extra : rebase_source : a3fa80a793a8a531e9f31c7097c2b2451020d724