Restrict to "loadable" URLs. Also exclude blob URLs.

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

This reduces the size of `spoofingKeyboardInfoTable` from 4 KiB to 3 KiB,
saving of memory 1 KiB per process.

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

Better field packing reduces it from 48 bytes to 44 bytes on 64-bit.

This reduces the size of the `text` section by 14,288 bytes, due to
`gHistogramInfos` shrinking.

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

Better field packing reduces it from 48 bytes to 40 bytes on 64-bit.

This reduces the memory used by each process by 336 bytes on 64-bit.

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

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

Bug 1658042 attempted to identify keys that could only handle legacy crypto
using CryptFindCertificateKeyProvInfo. However, it appears that this API can
be incredibly slow and potentially involve network I/O. This patch reworks
the legacy crypto handling by using CryptAcquireCertificatePrivateKey with the
CRYPT_ACQUIRE_SILENT_FLAG flag to avoid showing UI at inopportune times.

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

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

2020-09-18  Kevin Jacobs  <kjacobs@mozilla.com>

        * automation/abi-check/previous-nss-release, lib/nss/nss.h,
        lib/softoken/softkver.h, lib/util/nssutil.h:
        Set version numbers to 3.58 Beta
        [c28e20f61e5d] [tip]

        * .hgtags:
        Added tag NSS_3_57_RTM for changeset cf7e3e8abd77
        [a963849538ca] <NSS_3_57_BRANCH>

        * lib/nss/nss.h, lib/softoken/softkver.h, lib/util/nssutil.h:
        Set version numbers to 3.57 final
        [cf7e3e8abd77] [NSS_3_57_RTM] <NSS_3_57_BRANCH>

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

I will land a testcase separately once I manage to write something that triggers the arguments rectifier code and doesn't use Intl.

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

Bug 1665527 - part4 : add new testcase for 'browser_stop_control_after_media_reaches_to_end.js'. r=chunmin

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

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

Because of D90771, we need media session to notifty its status correctly in order to deactivate the controller. Therefore, when its document becomes inactive (in bfcahce), we should treat media session as inactive and notify it to `MediaStatusManager` in order to clear the active media session if needed.

In addition, add some assertions to ensure we won't modify or set any attributes on media session when its document is inactive.

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

Bug 1665527 - part1 : deactivate a controller only when it doesn't have controlled media and active media session. r=chunmin

Currently, we only keep controller active when it has controlled media. That strategy works well for non-media session situation because only controlled media need to listen to media keys.

However, when having media session, thing goes slightly different. When we don't have any controlled media, active media session may still listen to media keys and do the corresponding operation. Therefore, we should keep the active media session being able to receive media keys even if the controlled media has gone and deactivate a controller when it doesn't have controlled media and no active media session.

Example, play a audible media first, then press `next track`, if media session is going to play an inaudible media (which is not a controllable media, so no controlled media is existing), we still want media session to receive and handle media keys for users.

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

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

This doesn't change the behavior because we remove the
`aMinSizeFallback=true` use case in the previous part.

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

Bug 1316534 Part 6 - Update flex item's transferred size suggestion implementation to match the spec. r=dholbert

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

Bug 1316534 Part 5 - Update flex item's specified / content size suggestion implementation to match the spec. r=dholbert

Spec reference:
https://drafts.csswg.org/css-flexbox-1/#min-size-auto

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

test_dynamic_reflow_root_disallowal.html: in the next part, we can calculate
`min-size:auto` as the minimum of specified size and content size correctly
regardless of the value of `flex-basis`. If we do not reset the `inline-size`
(or `block-size`) to `auto`, the flex item's min-width (or min-height) will
always be its specified size (`width:10px` or `height:10px` set in
`gReflowRootCandidateStyles`), and changing `inner` to the content size from
`width:20px` to `width:40px` will have no effect.

flex-minimum-{width,height}-flex-items-005.xht: To make the flex item
resolve min-height:auto as the specified size, the content (image) size
must be larger than it. So here we change the image size to 200x200.
Google Chrome can also pass this test after this patch.

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

Bug 1316534 Part 3 - Make ComputeSizeWithIntrinsicDimensions() respect ComputeSizeFlag::UseAutoBSize. r=dholbert

nsIFrame::ComputeSize() respects UseAutoBSize, and so should
ComputeSizeWithIntrinsicDimensions(). This is essential in order to pass
layout/reftests/w3c-css/submitted/flexbox/flexbox-min-height-auto-002{a,c}.html
and flex-aspect-ratio-img-column-011.html [.flexbox 7] after updating
specified / content size suggestion in a later part.

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

Flex item's intrinsic size can affect the content size suggestion in the
automatic minimum size resolution, so we shouldn't optimize the reflow
away. https://drafts.csswg.org/css-flexbox-1/#min-size-auto

Add `IsFlexItem()` condition to the methods to avoid set
`IMAGE_SIZECONSTRAINED` bit in `nsImageFrame::Reflow()`. So after
decoding the image and updating its intrinsic size, we'll reflow the
flex item again.

This is needed to pass
testing/web-platform/tests/css/css-flexbox/flex-minimum-width-flex-items-013.html
after updating specified / content size suggestion in a later part.

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

Bug 1316534 Part 1 - Removed unused arguments to nsIFrame::ComputeISizeValue() computing LengthPercentage ISize(). r=dholbert

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

We use it to merge blobs, but that doesn't match the spec. Per:

  https://html.spec.whatwg.org/#the-list-of-available-images

We should key off the URI, and thus a revoked image should be able to be
reused if the request is cached. This works to allow printing revoked
blob images, which other browsers allow.

I don't see any way to make that work easily while preserving the blob
image optimization. That being said, it seems other browsers also
re-decode when creating different URLs for the same blob (see the
test-case attached to the bug), so it seems we should be able to live
without it.

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

Bug 1666619 - test_XHRDocURI.html may leave unprocessed history.back() operation after SimpleTest.finish() call, r=jesup

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

Backed out changeset 994c13da52dc (bug 1664719) for wrench failures on text-fixed-slice.yaml. CLOSED TREE

Backed out changeset 031b4f94e7f7 (bug 1658937)
Backed out changeset 8d6b4239dacb (bug 1658937)
Backed out changeset 9d9674f18f0c (bug 1658937)

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

It is no longer used.

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

This patch changes the picture cache logic to create a new slice
if it finds a primitive with an incompatible set of shared clips.

In testing, I have been unable to find any real world content that
hits this case. There is a single test case in CI that hits this
case, which confirms that a new slice is created correctly. Due
to this, it should have minimal effect on real world browsing.

The benefit of this is that we know the set of shared clips won't
change as we continue to build the scene. The follow up patch to
this can then filter out and remove shared clips from primitives
during scene building, rather than frame building.

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

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

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

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

Depends on D91028

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

Bug 1637908 - Add some tests for the touchable heuristic to the existing event radius tests. r=snorp

Depends on D91027

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

The existing heuristics in GetClickableAncestor have evolved over time to be
quite specific to mouse/click events, because those are the ones that we have
enabled by default. The heuristics we want for touch events are different and
should generally be very conservative, because we almost never want to retarget
the raw touch events. This patch introduces a new GetTouchableAncestor
function that implements this new conservative heuristic function and uses it
for determining the retargeting destination for touch events.

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

Depends on D91025

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

There's a few early-return conditions where we don't need to do this computation
at all. So this patch just moves the computation to after the early-returns. No
functional changes intended.

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

Bug 1665445: install-moz-phab installs the Phabricator credentials r=firefox-build-system-reviewers,rstewart

Since `install-moz-phab` is meant to simplify the moz-phab setup flow,
automatically prompting for Phabricator credentials removes an otherwise
manual step.

Detecting the "console_script" location of a package in a
cross-platform, virtualenv-supporting and "--user"-supporting way is
tough, and the most consistent solution seems to be to list the package
contents of moz-phab and look for the one that seems to be the entry
point.

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

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

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