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

The immediate effect is to make any image larger and more prominent.
This might not be the right option for regular DOM notifications,
which support only `icon` (and not `image`) in Firefox at this time,
but we can adjust (perhaps limiting the generic template to privileged
alerts) as we need in the future.

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

Bug 1788960 - Part 2: Telemetry event when completing chrome-privileged Windows native notification with `name`. r=chutten

This allows to connect a `backgroundTaskMessage` popping a toast
notification with a given `name` through to a re-engagement with
Firefox.

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

On Windows, when an alert is privileged and `name` is non-empty, round
trip its `name` (as `privilegedName`) through the Windows notification
mechanism, and provide it to the "relaunch" callback.

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

Backed out changeset d6a154ada951 (bug 1781434)
Backed out changeset 0ddeff2468d8 (bug 1781434)

Bug 1790518 - Enable video overlay until early beta on non-Intel GPU on Windows r=jrmuizel,gfx-reviewers

With early beta, the video overlay could be tested more.

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

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

- add struct.new, .new_default instructions
- add array.new, .new_default, .new_fixed instructions

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

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

The regressing bug accidentally swapped the foreground / bg colors in a
way such that it doesn't look like there's an outline.

Do some adjacent clean-up while at it, and add a test.

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

Backed out 3 changesets (bug 1786399, bug 1779645) for causing reftest failures on page-name-zero-height-001.html. CLOSED TREE

Backed out changeset 81c8d6a2d6f9 (bug 1786399)
Backed out changeset 3ee5fb016aa0 (bug 1779645)
Backed out changeset b626e11a262d (bug 1779645)

Bug 1789344 - Make `SelectionState::DidMoveNode` track DOM points having pointed the moved content correctly r=m_kato

When selection is `abc<b>[def</b>]ghi`, `insertParagraph` command will delete
the `<b>` element first, then, `Selection` becomes `abc{}ghi`.  Then,
`HTMLEditor::InsertParagraphSeparatorAsSubAction` wraps all of the line in
the default paragraph, `<div>`, with
`HTMLEditor::FormatBlockContainerWithTransaction` (although this is incompatible
behavior with the other browsers).  At this time, new `<div>` is inserted before
the first text node and then, move the text nodes into the new `<div>`.

However, `RangeUpdater::DidMoveNode` just slides the offsets if containers of
registered DOM points are the ex-parent of the moving nodes.  Therefore, the
tracked selection range in `HTMLEditor::FormatBlockContainerWithTransaction`
become `<div></div>abc{}def`, then, `<div>abcdef</div>{}`, but the expected
behavior is of course, `<div>abc{}def</div>`, then, split the new `<div>`.

So the problem is, `DidMoveNode` assumes that DOM points won't point the moving
content node.  If the node is pointed, it should keep pointing in the new
parent.

Note that the expectations of new tests are based on Chrome, therefore, the
new known failures are incompatible with Chrome.

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

The page-name property only applies to boxes which can create class A
breakpoints. One of the qualifiers for this is a block-level item, which is
the child of a block frame. Additionally, page-name propagation only occurs
through frames for which the page-name property applies, because where it does
not apply the auto page-name is propagated instead.

This means we only need to worry about block frames, and only use specified
page-name for BlockOutside frames.

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

This adds test for replaced frames which have block layout, frames with zero
content-height, inline-block frames, and vertical and orthogonal writing modes.

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

Bug 1779645 Part 1 - Switch CSS named page fragmentation to happen at reflow instead of frame construction r=dholbert

This also adds a small post-processing step for frame-construction to ensure
that replaced frames (or more generally frames with content but no children)
have the auto page-name set on them.

When page-name value tracking is switched to be lazy, this post-processing step
will likely be redundant and can be removed.

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

Bug 1788790 - Using TimeDelta instead of TimeStamp to allow for negative values when given non spec ntp;r=pehrsons

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

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

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

Make it a bit easier to read and less prone to race conditions. Remove a
setTimeout referencing bug 103197 which I'm pretty sure it's not an
issue.

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

Depends on D156241

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

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

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

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

Bug 1790331 - Clarify why pre-loading of oleaut32.dll is necessary. r=bobowen,media-playback-reviewers,alwu

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

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

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

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

I also cleaned up browser_aboutwelcome_multistage_mr.js so that each task is
idempotent and does not pollute the state of other tasks (e.g., by leaving
prefs set).

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

What we are doing:
- Disabling the view/main-fenix and the cpu-memory jobs

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

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

Bug 1786927 - Consolidate the way we trigger autocomplete popup in tests. r=credential-management-reviewers,sgalich

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

We enable the sanitizing, which will omit the value in the
content process and trigger event telemetry - but we won't
crash the process.

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

Bug 1789421 - Generate crash reports for content process shutdown hangs only when we can confirm that the process did not shut down in time r=jstutte

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

dsb -> dce20589cb2b50184b90c2ba268deb7ae7607e9c
el -> 93b03feb3781aa3bfb368a22e4141c158a75b0c8
fi -> ee708cf4cb4b69da19503a153ed364915c188328
fr -> 10590b4850974ae25902260b3470dde958a7e709
he -> 7b779cfedacb2ee09158ebad8c092d54ddc879d6
hsb -> 88061c0806a5ee259f381b85bc7ffb5bc9da6363
hu -> f518d16bfae6e0e025d5345e5e42f48b29c76d8e
ia -> 75edcbb9ccc4540cbebc9b3280aa32e2616a72c0
kab -> 68833491b3ad425d8d58fb878e4700b2e899fb50
ko -> 095264e2a58972eeb8869c619ab8c68ad03b65b7
lo -> b4a40798001e3c9728db045423f142ebc7402008
nb-NO -> 511b77203d9996bfd7b1cc8b30a6cfa59dfea4b7
nn-NO -> 26300c62e29acffe00ff37672de5ad9de0026f1b
pt-BR -> ef938c665534c91cf42d981c331ab56a30b73629
pt-PT -> c21930309ca6b97bfb1fd2533e32fc870dcfdbe2
rm -> 3d9909e64c0bd82629ee71f9ee50a9260dadb84b
ro -> 810ae99530cb5b0174f02c582a47ca44793fca83
ru -> 9f7799b135bd485ae90f4cfbb3a8bfb1a73e826b
sk -> b142a5722b24b87013f2dc390b92c6c4d7546971
sl -> 12862f3a06eac20a666b2c86e368676ae6f71398
te -> 3474c18c64036e42981b78e31581182080415331
tg -> 782228966a3f0f80ea33b2437801d4380f659320
zh-CN -> a56db11b90878da1fee63443d2393af299cc1334
zh-TW -> 3230bc1cd94d3b8434d3a1cdfdcd70f716ea2da2

In the recent refactor of this (https://bugzilla.mozilla.org/show_bug.cgi?id=1782295) I managed to break our ability to create shortcuts if they don't already existed. This was caused by two things:
1) An errant `NS_SUCCEEDED` call remained after the call it was checking moved elsewhere (oops)
2) The taskbar pinning code was not updated to set the shortcut file path (required after the refactor).

This patches fixes both of those issues. Note that all the directory service interaction is done on the main thread, because the actual function doing the work is on a background thread, and the directory service does not work there.

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

This was an oversight during the original implementation in bug 1761291. I updated the code that creates shortcuts there, but not the code that looks at existing ones.

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

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

In days of old, it was safe to use -brand-short-name for this, as it always lined up with the installer's concept of BrandShortName. This changed when https://bugzilla.mozilla.org/show_bug.cgi?id=1378834 landed -- which started using "Firefox Nightly" for the nightly branding BrandShortName in the installer (but maintained "Nightly" as the in-product -brand-short-name). Changing one or the other of these is not really a viable option:

- Changing the installer's BrandShortName for Nightly to match -brand-short-name would cause shortcuts to simply be called "Nightly" -- which is the opposite of what the aforementioned bug wanted
- Changing -brand-short-name would cause a number of in-product strings to start using "Firefox Nightly" instead of "Nightly" -- which is probably undesirable for a few reasons, not the least of which is possible l10n implications

For these reasons, and the relatively short timeline I have to fix this, I'm taking the simplest and easiest path of introducing a new string specifically for in-product shortcut names, which lines up with the installer's values for BrandShortName. (We perhaps should also separate this out in the installer -- but it's unnecessary here, so I did not go to the trouble.)

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