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

Non-MSIX notifications are not removed when Firefox is uninstalled. To handled this we've added a new `uninstall` background task and extended `nsIWindowsAlertService` to deregister notifications on uninstall.

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

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

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

It seems that getAllByTypes results aren't in a stable order when
the test is run with --verify.

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

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

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

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