Bug 1640223 - Expand the given size in ExpandHeightForViewportUnits by multiplying the 'vh value / visible area height'. r=botond

The viewport units size doesn't match the aspect ratio of the screen size in
some cases.

For example, in the case of the reftest in this commit, the meta viewport is
"width=1600, height=device-height" and the screen size during reftest is
"800x1000". Thus the viewport units size will be "1600x1000". In such cases
with the old way ExpandHeightForViewportUnits shrinks the given size
"1600x1800" to "1600x1000" with 100px dynamic toolbar max height (and the
MOZ_ASSERT in the function happens on debug builds).

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

As all versions of zlib >= 1.2.3.1 have a pkg-config file, and 1.2.3.1
is close to 14 years old, let's drop 1.2.3 and just use pkg-config, which
simplifies what we need to do dramatically.

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

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

The index is not protected by scopes, so don't use the proxy to access it

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

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

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

Bug 1598026 - separate listening for accessibility lifecycle events between parent and content. r=mtigley

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

2020-05-29  J.C. Jones  <jjones@mozilla.com>

	* lib/nss/nss.h, lib/softoken/softkver.h, lib/util/nssutil.h:
	Set version numbers to 3.53 final
	[7e453a5afcb4] [NSS_3_53_RTM] <NSS_3_53_BRANCH>

2020-05-28  Kevin Jacobs  <kjacobs@mozilla.com>

	* .hgtags:
	Added tag NSS_3_53_BETA2 for changeset 8fe22033a88e
	[90c954f62c9d]

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

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

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

This change makes a set of probes keyed. The key is "(default)" if no steering
is currently active, or "(auto-detected)" is the current URL has been set
by steering (autodetection).

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

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

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

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

Backed out changeset 9e0971e05ec0 (bug 1640734) for Browser-chrome failures in browser/components/newtab/test/browser/browser_asrouter_group_frequency.js. CLOSED TREE

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

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

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

Bug 1641361 - [wpt-sync] Update web-platform-tests to cbfde04695a79256d42991513c83a7b97dc14fcd, a=testonly

MANUAL PUSH: wpt sync bot

wpt-head: cbfde04695a79256d42991513c83a7b97dc14fcd
wpt-type: landing

Automatic update from web-platform-tests
[wpt] Fix css-contain "replaced" tests.

These tests were inadvertently testing our UA stylesheet for the audio
element. In our UA stylesheet we have:
audio {
  width: Xpx;
  height: Ypx;
}

which means that the intrinsic size tests are failing. This fixes the
tests to change the width/height when appropriate to "auto".

There is probably a discussion which needs to be had about the UA style
for the audio element, but not today.

Bug: 960385
Change-Id: I3c5e1362015dec9cc95b7f4683a552e4afcc7424
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212635


Commit-Queue: Koji Ishii <kojii@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#771803}

--

wpt-commits: cbfde04695a79256d42991513c83a7b97dc14fcd
wpt-pr: 23774

Automatic update from web-platform-tests
[EventTiming] Use polling in performance.eventCounts test

It looks like actions.send() does not wait for the events to get
processed in order to resolve the promise, which means eventCounts may
not be populated by the time we begin testing it. Hence, in this CL we
perform a polling-based approach. Sample failure:
https://isolateserver.appspot.com/browse?namespace=default-gzip&digest=8e7df6aa16ccbffabef2b11c5f2d9aaa02d396c1&as=layout-test-results%5Cexternal%5Cwpt%5Cevent-timing%5Cmouseover-actual.txt

Bug: 1074048
Change-Id: I58629d66ad146fd435fc95fb875f21a96f5470a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212497

Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#771778}

--

wpt-commits: 546dd707ac9440acfc40a326837a1e4032e0a2ff
wpt-pr: 23758

Bug 1639938 [wpt PR 23731] - Reduce cross frame messages in feature-policy-nested-subframe-policy.https.sub.html, a=testonly

Automatic update from web-platform-tests
Reduce cross frame messages in feature-policy-nested-subframe-policy.https.sub.html (#23731)

Previously each 1st level subframe will post 6 messages to main frame.
This CL reduce the message send to to main frame to 1 message,
effectively improve the test speed.

Change-Id: I20dcbe3a74aa9359185c61673ff1b5e39a1eea68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212486


Commit-Queue: Charlie Hu <chenleihu@google.com>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#771658}
Co-authored-by: Charlie Hu <chenleihu@google.com>
--

wpt-commits: 2228dbdd370235f8bad3330aaec613f9d3ec6ac7
wpt-pr: 23731

Automatic update from web-platform-tests
Load pending resources after style adjustments.

We don't fetch resources for ComputedStyle which is in a display:none
subtree or display:contents since [1]. Style adjustments are done to the
display type in the StyleAdjuster and we need to make sure we load
resources where display changes from a non-rendered value to a rendered
one after style adjustments.

Specifically, this happens with blockification of :root elements which
are display:contents.

[1] https://crrev.com/caf740f6c0b57ca102026f40f3cc62f9f3cf5159

Bug: 1085750
Change-Id: I7686c6f8bf4918bec5812d1bf893ad2c4cb9262c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214897

Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#771748}

--

wpt-commits: 1c152f0e99b4ae9f10b62b70007821b072b00f75
wpt-pr: 23765

Bug 1634749 [wpt PR 23363] - Python 3: Port some html tests following Python file handlers p…, a=testonly

Automatic update from web-platform-tests
Python 3: Port some html tests following Python file handlers porting guide (#23363)

This is a rework on https://github.com/web-platform-tests/wpt/pull/22402
This change follows the porting guide discussed in RFC49:
https://github.com/web-platform-tests/rfcs/pull/49

Co-authored-by: Robert Ma <bob1211@gmail.com>
--

wpt-commits: e60c41610959f414e24fe2360151d94953436906
wpt-pr: 23363

Bug 1640742 [wpt PR 23761] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=212054, a=testonly

Automatic update from web-platform-tests
Use Ahem font in multi-line-wrap-reverse-column-reverse.html (#23761)

css-flexbox/flex-lines/multi-line-wrap-reverse-column-reverse.html:
  * Update the test to use the Ahem font, and rely on different font colors
    (instead of different glyps) to check that each box of the test is placed
    correctly.

Export of: https://bugs.webkit.org/show_bug.cgi?id=212054
--

wpt-commits: b2d87a14271da903e5897779f623c74e8601f36e
wpt-pr: 23761

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

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

Bug 1641962: Defer imports of distutils.util to ensure bootstrap can run r=rstewart,perftest-reviewers,sparky

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

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

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

Bug 1640734 - Frequency capping should apply separately for production and experiment messages r=k88hudson

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

Depends on D77522

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

Depends on D77521

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

Depends on D77514

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

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

Bug 1633866 - [taskgraph] Create a system to choose how test manifests are loaded via a parameter, r=tomprince

Currently test manifests are loaded by instantiating a TestResolver and
traversing moz.build files to find manifests.

With 'manifest-scheduling', we'll want to grab the manifests directly from the
bugbug service instead. Initially we'll want to enable manifest-scheduling with
|mach try auto|, but not on autoland yet.

This patch will allow |mach try auto| to set the parameter that causes bugbug
to be used (see future commits in this bug).

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

We create sub images from larger images by using a stride that matches
the original and adjusting the offset. This creates a situation where
the last row will only have stride - offset bytes. This stops us
from lying to CGDataProvider.

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

Waiting for engines to be reloaded before checking the cache, can cause the test to miss the cache notification.

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

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