Backed out changeset 2c6bb36b0667 (bug 1170668) for causing build bustages on TestShortRead.cpp CLOSED TREE

Bug 1782924 - Avoid crash writing Firefox Messaging System targeting information at shutdown. r=application-update-reviewers,bytesized

I tested this as much as I could locally -- hence the `dump`
workaround -- but I have no particular suggestion for how to test this
in automation.  Even triggering the targeting snapshotting during
shutdown requires the timers and shutdown process to line up in a way
that's not trivial to guarantee.

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

Bug 1772024 Part 2: Fix clause for Apple Silicon for video specialize pref. r=gfx-reviewers,lsalzman

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

Similar to https://phabricator.services.mozilla.com/D153115, but for geckodriver.

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

Bug 1775503 - [devtools] Prevent showing content process request when the browser toolbox focuses on the parent process. r=bomsy

This is still one blind spot with privileged request done by content processes.
They aren't related to any BrowsingContext/WindowGlobal and there isn't any
attribute on channel/loadInfo which helps knowing they originates from a content process.

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

Bug 1783934 - Add a chrome-only -moz-box-layout: legacy | flex, and use that to implement flexbox emulation. r=dholbert

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

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

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

This patch changes how nsConverterInputStream handles passing data
through to the underlying unicode converter in order to make it more
reliably handle propagating errors and deal with short reads from the
underlying input stream.

This was done by making the code continuously read within the Fill
method until at least one character has been decoded from the input
stream, so that we don't spuriously communicate an EOF to the caller due
to a short read not producing enough bytes for the decoder to produce a
UTF-16 character.

In addition, while making this change it became easier to signal to
the decoder about the final read from the input stream, meaning that
partial characters at the end of the stream will now generate a
replacement character, rather than being ignored.

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

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

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

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

This patch contains the bulk of the implementation of the modal. Most of
it is UI work and wiring together the various components. There is a bit
of complexity in the clustering algorithm, as I implemented the DBSCAN
algorithm to help cluster the text recognition results.

I filed Bug 1782586 to improve the DBSCAN algorithm, but currently it
works the same as the algorithm is described on Wikipedia.

Note that the tests are in the following patch in order to keep the line
count small for this patch.

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

The implementation follows after this, but I felt it made the code
easier to read to by splitting it out.

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

Bug 1782578 - Rename and move the context menu for text recognition r=nordzilla,fluent-reviewers,flod

This matches what is in the Figma spec.

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

This code will most likely be removed, but for now I am putting it
behind a pref so that it won't be activated when the modal is being
created.

See Bug 1782582 for the removal of the code.

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

This test seems to fail frequently on Linux without Fission, and on Android,
when the parent controlled navigation pref is enabled, so disable the test
there. We don't really support non-Fission builds anyways, and apparently
containers aren't supported on Android.

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

MANUAL PUSH: Test-only trivial fix CLOSED TREE

MANUAL PUSH: Orange fix CLOSED TREE

Bug 1398792 - [wdspec] Enhance "Get Element Property" tests for Web References. r=webdriver-reviewers,jdescottes

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

Bug 1398792 - [marionette] Waive Xrays in "WebDriver:GetElementProperty" to get unfiltered access to untrusted elements. r=webdriver-reviewers,jdescottes

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

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

Backed out changeset 44255b7d9b1c (bug 1746524) for causing xpcshell failures on test_ext_userScripts_register.js CLOSED TREE

I can't reproduce this on Linux (which would make it easier to dig into what's
going on), but I confirmed this fixes the issue on Windows.

The flexing algorithm of XUL doesn't deal well with the footer block.

This shouldn't be needed, I think, because the listbox height is handled
explicitly in

  https://searchfox.org/mozilla-central/rev/6a37a2ab9328bec6a29f688d1b2fba6974d34905/toolkit/content/widgets/autocomplete-popup.js#361

Also use CSS rather than attributes to flex stuff.

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

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

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

Backed out 6 changesets (bug 1782578, bug 1782579) for causing mochitest failures on browser_parsable_css.js CLOSED TREE

Backed out changeset bdb42cfe6213 (bug 1782579)
Backed out changeset 5f17ee4cc4df (bug 1782578)
Backed out changeset 4f969d46dd37 (bug 1782578)
Backed out changeset b4c51d1ffa99 (bug 1782578)
Backed out changeset 98d0d6bcd37b (bug 1782578)
Backed out changeset 8332d678079e (bug 1782578)

Backed out changeset 449fe2d946ea (bug 1783934) for causing mochitest failures on test_animation-type-longhand.html. CLOSED TREE

Bug 793686 Part 2 - Call SetNextInFlowNeedsReflow() when an absolute containing block is incomplete. r=emilio

This fixed the following assertion for `layout/forms/crashtests/1690166-1.html`
after applying part 1.

```
ASSERTION: We have to create a continuation, but the block doesn't want us to reflow it?
```

https://searchfox.org/mozilla-central/rev/c0bed29d643393af6ebe77aa31455f283f169202/layout/generic/nsColumnSetFrame.cpp#750-752

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

According to `nsContainerFrame::ShouldAvoidBreakInside`, we allow a frame to
break from inside when it is at the top of page/column, i.e. when `mIsTopOfPage`
is true.

This patch allows the content at the top of the column to honor the
break-inside:avoid during column balancing, so it can now propagate the
break-before status to nsColumnSetFrame if it needs to report such status.

We don't need to worry about disallowing an break-inside:avoid content from
breaking will trap the column balancing algorithm forever. If the content's
block-size is larger than the column container's available content-box
block-size, then the column balancing algorithm will give up and fill the
columns sequentially at
https://searchfox.org/mozilla-central/rev/4f2984be127d2e7c788cf1848d63dca63022beec/layout/generic/nsColumnSetFrame.cpp#1146-1162

The reference files are modified to reflect the rendering as of this patch. Note
that browsers do not agree on the rendering of `1420528-1.html`. Before this
patch, our rendering is the same as Chrome by placing "Spacer" in the first
column, but now we agree with webkit by placing it in the second column.

The multicol in `611574-2.html` is used for visual separation of subtests. I
change it from column balancing to fill to workaround bug 1784002.

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

Similar to the fix done for values in Bug 1590031, now focused on property names.

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

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

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

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

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

This patch contains the bulk of the implementation of the modal. Most of
it is UI work and wiring together the various components. There is a bit
of complexity in the clustering algorithm, as I implemented the DBSCAN
algorithm to help cluster the text recognition results.

I filed Bug 1782586 to improve the DBSCAN algorithm, but currently it
works the same as the algorithm is described on Wikipedia.

Note that the tests are in the following patch in order to keep the line
count small for this patch.

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

The implementation follows after this, but I felt it made the code
easier to read to by splitting it out.

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

Bug 1782578 - Rename and move the context menu for text recognition r=nordzilla,fluent-reviewers,flod

This matches what is in the Figma spec.

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

This code will most likely be removed, but for now I am putting it
behind a pref so that it won't be activated when the modal is being
created.

See Bug 1782582 for the removal of the code.

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

* Enable testing using Ion
* Disable call_ref.js for ion
* Allow Ion when --wasm-function-references
* Fix WasmOpIt to pass ref values
* Add br_on_null, br_on_non_null, ref.as_non_null

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