Bug 1645528 - Connect nsRefreshDrivers in content processes with a widget-local vsync source r=mattwoodrow,emilio

To allow `requestAnimationFrame()` and similar things to run at monitor
speed if there is only a window-specific vsyncsource available.
This is the case for Wayland and, in the future, EGL/X11. Other backends
may opt for window specific vsyncsources as well at some point.

The idea is to, instead of using global vsync objects, expose a vsyncsource
from nsWindow and use it for refresh drivers. For the content process, move
VsyncChild to BrowserChild, so for each Browserchild there is only one
VsyncChild to which all refresh drivers connect.

IPC in managed either by PBrowser or PBackground. Right now, PBrowser is
only used on Wayland, as both PBrowser and the Wayland vsyncsource run
on the main thread. Other backends keep using the background thread for
now.

While at it, make it so that we constantly update the refresh rate. This
is necessary for Wayland, but also on other platforms variable refresh rates
are increasingly common. When using PVsync, limit updates to once in every
250ms in order to minimize overhead while still updating fast.

How to test:
 - run the Wayland backend
 - enable `widget.wayland_vsync.enabled`
 - optionally: disable `privacy.reduceTimerPrecision`
 - run `vsynctester.com` or `testufo.com`

Expected results:
Instead of fixed 60Hz, things should update at monitor refresh rate -
e.g. 144Hz

Original patch by Kenny Levinsen.

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

This was accidentally enabled when moving to the more modern print dialog API.

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

This also implements an improved error message:
> TypeError: RegExp.prototype.global getter called on non-RegExp object: Math
This is similar to Chromes' message:
> RegExp.prototype.global getter called on non-RegExp object

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

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

The external texture we create in WebGPU to present the canvas was taking
a different path on macOS with specific resolutions:
https://searchfox.org/mozilla-central/rev/85b84f82489451362a351b144fe5232a8e46c61c/gfx/layers/composite/TextureHost.cpp#590

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

Bug 1678108: Invalidate DisplayItemCache entries when nsDisplayItem::RestoreState makes a change. r=miko

Partial fix.

If nsDisplayItem::RestoreState changes the state of an nsDisplayItem, that
invalidates any prior RetainedItems items sent to WebRender for it, and its
DisplayItemCache entry is invalid. Clear the cache index in the
nsDisplayItem.

RetainedDisplayListBuilder::PreProcessDisplayList doesn't have convenient access
to the DisplayItemCache, so don't clear the cache entry in the DisplayItemCache.
The cache itself will eventually realize the entry is unused and clear it.

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

This allows mesa to continue using the existing vsync implementation.

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

Bug 1662977: Allow "maximumFractionDigits" option in Intl.NumberFormat to be less than the default minimum fraction digits. r=yulia

Implements the changes from the "has consensus" PR <https://github.com/tc39/ecma402/pull/471>.

The second pair of `DefaultNumberOption()` calls was inlined, because only the
fallback case is relevant anyway. Steps 12.d and 12.e from the spec PR were
combined into a single `if`-block. That way it also matches step 12.f more
closely.

Also changed the single `if` steps into an `if-else if` chain, because the
steps are mutually exclusive.

Depends on D95734

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

Implements the changes from the "has consensus" PR <https://github.com/tc39/ecma402/pull/459>.

Drive-by change:
- Enable a named groups RegExp test which wasn't enabled when bug 1362154 was implemented.

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

The fallback code is no longer required.

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

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

Regenerated the patch behalf of zawertun user.

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

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

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

Bug 1673931 - reinstate nsContentUtils #include "nsIURIWithSpecialOrigin.h" which is used by Thunderbird. r=sg DONTBUILD

From https://hg.mozilla.org/mozilla-central/rev/85bdc36c7591ae83275321c078d2183bf422c592

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

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

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

Depends on D97753

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

The RDD process can no longer work without having access to win32k ; enabling this pref would lead to a crash on Nightly and failure to work elsewhere.

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

Bug 1677684 - part 2: Make `ContentCache` cache character rects in last commit composition string for undoing the commit r=m_kato

Usually, IME sets selection and considers candidate list position at starting
new composition.  However, Apple Japanese IME sometimes consider the candidate
list position at retrieving the character rects before setting selection.
Therefore, we need to store last commit string's character rects, but don't
need to store it in long time because Kakutei-Undo is supported by Japanese
IMEs and they work only immediately after committing a composition.  E.g.,
after moving caret, it won't be available.

Depends on D97838

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

Bug 1677684 - part 1: Make `ContentCache` manage composition start offset with `Maybe` instead of using a magic number r=m_kato

Currently, it manages the composition start offset with `uint32_t` and setting
it to `UINT32_MAX` when there is no composition.  But this is now rewritable
with `Maybe<uint32_t>` for easier to read.

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

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

Reported here: https://github.com/sylvestre/gecko-dev/pull/207/files

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

PR can be found here:
https://github.com/sylvestre/gecko-dev/pull/165

./mach lint -l flake8

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

Bug 1678314 - Add instructions to run mach lint to the contributors' quick reference. r=sylvestre,championshuttler DONTBUILD

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

PR can be found here:
https://github.com/sylvestre/gecko-dev/pull/309

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

Fix with:
$ ./mach lint -l codespell --fix

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

Bug 1679054 - Update dependency sphinx-copybutton to v0.3.1 r=firefox-source-docs-reviewers,championshuttler DONTBUILD

Reported here:
https://github.com/sylvestre/gecko-dev/pull/227

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

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

E.g. Blitting 1,1,-1,-1 to 0,2,2,0.
Some drivers have trouble with this.

Primarily tested by:
* conformance2/rendering/blitframebuffer-filter-outofbounds.html
* conformance2/rendering/blitframebuffer-outside-readbuffer.html

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

This commit adds a rosetta status to three different places:
- `nsSystemInfo`, to check for rosetta status per apple specifications. We also use the same check in `nsCocoaFeatures` in D89961.
- `Troubleshoot.jsm`, to add rosetta status data (should it exist) to use in about:support
- `About:Support` itself, if the device is running MacOS

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

Bug 1672091 - Disable the fade-in animation on macOS Big Sur, to work around a macOS bug (FB8828157) that causes the panel shadow to be missing. r=dao

The fade-out animation is kept.

To work around the bug, the first paint of the panel window needs to be done at
full window opacity. Reducing the window opacity after the shadow has been
computed works correctly.

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

We already explicitly warn if essential extensions are missing -
these warnings clutter debug logs quite a bit.

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

CLOSED TREE

CLOSED TREE

Backed out changeset bf721cd8ab14 (bug 1654817)
Backed out changeset fb1c314e6394 (bug 1654817)

Regenerated the patch behalf of zawertun user.

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

The fallback code is no longer required.

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