The bug occurs because some abspos children are split, but not being reflowed
again in the last column balancing reflow where the available block-size of the
last column might be unconstrained.

This patch makes the callers utilizing `ReflowInput::ShouldReflowAllKids()`
always reflow in the last column balancing reflow to ensure the correctness of
the layout.

Note: the `mIsInLastColumnBalancingReflow` flag is inheriting from parent to
child reflow input, but it will stop at the nested `nsColumnSetFrame` because
the nested one will create its own `ReflowConfig::mIsLastBalancingReflow` and
assign that flag when creating the reflow input for the children.

Bug 1837646 - disable browser_sma_show_migration_wizard.js on mac for frequent failures. r=aryx, a=test-only

Bug 1760081 - Disabled netwerk/test/unit/test_alt-data_simple.js on Windows for having a high failure rate. r=necko-reviewers,kershaw a=test-only

Bug 1817727 - Disable test_filename_sanitize.js on mac because of permafailures. r=aryx, a=test-only

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

Bug 1878182 - Instantiate Cairo scaled font for ScaledFontBase::GetPathForGlyphs. r=jfkthameApproved for 123 beta 8, thanks. a=pascalc

This bug likely dates back to bug 1584268, which makes it so that Cairo scaled fonts must be
instantiated on demand for their first use. It seems like some StrokeGlyphs machinery got
overlooked and somehow never caused a problem till now.

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

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

Backed out changeset eb8c2d5bd1aa (bug 1830071)

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

	Bug 1830071 - Ensure tasks run across all users in Windows r=bytesized,application-update-reviewers,nalexander a=pascalc

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

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

Original Revision: https://phabricator.services.mozilla.com/D198945

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

Original Revision: https://phabricator.services.mozilla.com/D200245

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

Backed out changeset 2c8561c8e416 (bug 1873866)

Original Revision: https://phabricator.services.mozilla.com/D199939

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

Bug 1875621 - SlicedInputStream::Serialize should serialize the outer SlicedInputStream as a pipe in the efficient path.  a=pascalc

Original Revision: https://phabricator.services.mozilla.com/D199852

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

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

Backed out changeset 39193ec581e4 (bug 1833814)

Original Revision: https://phabricator.services.mozilla.com/D195549

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

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

Original Revision: https://phabricator.services.mozilla.com/D197534

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

Bug 1874627 - regenerate expiring test certificates for 2024 (branch patch), this time with certificates included. r=jschank a=test-only


* the certificates were regenerated using `./mach generate-test-certs`
* the build/pgo/certs/ changes were made using
  `./mach python build/pgo/genpgocert.py`
* the zip files in security/manager/ssl/tests/unit/test_signed_apps/ were
  updated per the directions in the corresponding moz.build file
* security/manager/ssl/tests/unit/test_cert_override_read.js needed manual
  updating

These certificates and other test artifacts will now expire in 2025.

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

* the certificates were regenerated using `./mach generate-test-certs`
* the build/pgo/certs/ changes were made using
  `./mach python build/pgo/genpgocert.py`
* the zip files in security/manager/ssl/tests/unit/test_signed_apps/ were
  updated per the directions in the corresponding moz.build file
* security/manager/ssl/tests/unit/test_cert_override_read.js needed manual
  updating

These certificates and other test artifacts will now expire in 2025.

Test Plan:
https://treeherder.mozilla.org/jobs?repo=try&revision=04e3780551b5e83a70b51acd84e1b3383a249f14

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

distutils is no longer available in Python 3.12, which means we cannot
require it on bootstrap, otherwise we cannot bootstrap from Py 3.12.

We already require setuptools as part of mach's requirements, so it's
fine to depend on setuptools elsewhere.

Original Revision: https://phabricator.services.mozilla.com/D190537

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

Original Revision: https://phabricator.services.mozilla.com/D187541

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

distutils have been removed from Python 3.12, so replace it:

Sometimes using packaging's Version, sometimes providing our own in the
case of mozrelease/versions.py. Add more tests for the latter.

Original Revision: https://phabricator.services.mozilla.com/D190540

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

six -> 1.16
urllib3 -> 1.26.17

Original Revision: https://phabricator.services.mozilla.com/D190288

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

68.0.0 is the last version of setuptools that still supports Python 3.7, currently our minimum supported Python version. (It's dropped at 68.1.0 as it's not considered as a breaking change, which is surprising: https://setuptools.pypa.io/en/stable/history.html)

Original Revision: https://phabricator.services.mozilla.com/D190674

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

There's a `Cython` issue (https://github.com/yaml/pyyaml/issues/601) with `PyYAML` that breaks our `./mach vendor python` in versions of PyYAML `>5.3.1` and `=<6.0`. This issue has been resolved with `PyYAML` version `6.0.1`, and we can just safely upgrade to it (rather than downgrading to `5.3.1` (which has other issues).

Original Revision: https://phabricator.services.mozilla.com/D183818

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

Following the official migration guide from
https://docs.python.org/3/whatsnew/3.12.html#imp

Original Revision: https://phabricator.services.mozilla.com/D190465

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

While bug 1857470 is set to fix the problem with a pip upgrade, it is
going to take some time. In the meanwhile, we can just do the minimal
thing that makes things work well enough for a build to go through.

Original Revision: https://phabricator.services.mozilla.com/D196256

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

Bug 1878346: Avoid intermittent test failures in test_bug514732-2.xhtml by flushing layout before setting up MozScrolledAreaChanged event-handler.  a=pascalc

This patch doesn't change behavior; it's just making this test more robust.

Without this patch, we can occasionally get an unexpected MozScrolledAreaChanged
from the initial about:blank test-document, which throws off the test logic
and causes test failures and timeouts. See this bug comment for more details
on how that happens:
https://bugzilla.mozilla.org/show_bug.cgi?id=1878346#c0

Original Revision: https://phabricator.services.mozilla.com/D200492

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

Bug 1867886: Ensure that NotificationController can't re-register with the refresh driver after it's been unregistered in Shutdown.  a=pascalc

This is just a "belt-and-suspenders" invariant tightening.  Shouldn't impact
behavior at all, assuming that we don't call methods on NotificationController
objects that have been nerfed with Shutdown().

Original Revision: https://phabricator.services.mozilla.com/D195321

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

Bug 1867358 part 4: Add some release asserts (and upgrade an existing assert), to validate that NotificationController isn't still registered as a refresh observer when it's destroyed.  a=pascalc

If these assertions somehow fail, then we are probably doomed to crash anyway.
The new release assertions just make it so we'll crash in a controlled way,
with a more actionable backtrace, closer to the problem-spot.

This patch also removes one mDocument null-check that's becoming redundant
since it follows a release-assert that would make us abort if the pointer is
null.

Original Revision: https://phabricator.services.mozilla.com/D195042

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

Bug 1867358 part 3: Adjust NotificationController to avoid modifying mObservingState after Shutdown has been called.  a=pascalc

We can sometimes reach the code that this patch is touching, just we've been
shutdown (as can be seen by the fact that we have a null mDocument pointer); in
that case, it's problematic for us to be assigning 'mObservingState' here. The
mObservingState assignment is meant to be *undoing* the temporary assignments
earlier in the function, but in this post-Shutdown situation, it's actually
causing us to forget that we already unregistered as a refresh observer, in a
nested stack level's call to Shutdown().

I think this one place is the only mObservingState assignment that's got this
problem. The other mObservingState assignments should all be OK (they don't
need a "have we shut down" check), because they're all either:
a) modifying mObservingState to record an actual change that we just made to
our RefreshDriver registration,
...or:
b) immediately adjacent to code that dereferences mDocument, implying that
mDocument is known-to-be-non-null at that point, which means we know we haven't
been Shutdown.

This patch unblocks us from adding a release assert in the
NotificationController destructor in the next patch in this series. (Without
this patch, that assertion can be made to fail, via this inadvertent
mObservingState assignment.)


Original Revision: https://phabricator.services.mozilla.com/D195200

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

Bug 1867358 part 2: Assert that EventQueue's mDocument member is initialized to something non-null.  a=pascalc

This patch is non-functional; it's just adding a debug-only assert, for
documentation and lightweight validation purposes.

As far as I can tell, the asserted condition must hold, since it looks like
this constructor is only invoked via this instantiation of the subclass, which
passes `this` as the aDocument arg (and `this` must trivially be non-null):
https://searchfox.org/mozilla-central/rev/12ea2c521cdd071a6d25b0894f31f8f23b18b76a/accessible/generic/DocAccessible.cpp#422

This assertion makes it easier to reason about the usages of this member-var.
There are lots of checks for whether mDocument is nullptr, and it's useful to
know that it'll always be non-null to begin with (though it becomes null
eventually, as part of teardown, when NotificationController::Shutdown is
called).

Original Revision: https://phabricator.services.mozilla.com/D195041

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

Bug 1867358 part 1: Fix up unbraced single-line if-statements in NotificationController and its superclass.  a=diannaS

This patch has no functional change; it's just some trivial fixups to align
with with Mozilla C++ coding style.

Original Revision: https://phabricator.services.mozilla.com/D195040

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

Bug 1713619 - ESR 115: Exempt chrome/resource principals from canvas randomization/placeholders. r=lsalzman a=pascalc

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