Bug 1905512 - Modify regex to allow an optional trailing dot at the end of URLs in history removeByFilter function.  a=RyanVM

Original Revision: https://phabricator.services.mozilla.com/D216355

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

Original Revision: https://phabricator.services.mozilla.com/D219733

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

Depends on D219752

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

Bug 1908095 - [devtools] removeSessionDataEntry for webextension toolboxes and watcher targets  a=RyanVM

Fix removing breakpoints in webextension toolboxes and watcher targets, add tests to cover both scenarios
Implementation update to fit 128 ESR

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

The patch comes from https://gitlab.com/redhat/centos-stream/rpms/firefox/-/merge_requests/94

Firefox isn't currently handling window focusing right on X11... There's a few problems:

If no startup id is provided, it tries to get user time from g_get_monotonic_time when there's no guarantee that timestamp is synchronized or even in a compatible unit. This merge request addressed that by dropping the code that uses g_get_monotonic_time entirely, and instead adding a heuristic to synthesize a startup id based on the time of the last user interaction on the display. This makes an assumption that firefox was started as a result of user interaction, which might not always hold true, but it's more likely than not, and is basically the same assumption firefox is already making by trying to use a timestamp of "now" (g_get_monotonic_time) when focusing the window.

If a startup id is provided, it fails to tell gtk to use it when focusing the window because it calls gtk_window_present_with_time with some other random timestamp instead of passing GDK_CURRENT_TIME (which is the magic value that means "use startup id for timestamp"). This commit tries to detect when a startup id is available, and the display is X11, and if so use a timestamp of GDK_CURRENT_TIME.

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

Bug 1908393 - Only hold strong references to BounceTrackingState in BrowsingContextWebProgress. r=nika,anti-tracking-reviewers,timhuang a=RyanVM

This ensures that the lifetime of a BounceTrackingState is tied more closely to the lifetime of a tab.

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

Bug 1902227 [Linux/VA-API] Backport AV1/VA-API playback fix for AMD/mesa > 24.0.7 r=padenot a=RyanVM

Backport of https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29400
Allows to use multiple slices for AV1 VA-API decode.

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

Bug 1896901 - Don't use an <input> for unknown content type file. r=dao,desktop-theme-reviewers a=RyanVM

This happens because the input minimum size doesn't depend on the value
text. There's an experimental CSS property to support something like
this, field-sizing:

  https://developer.mozilla.org/en-US/docs/Web/CSS/field-sizing

Which is tracked on bug 1832409, but which we don't implement yet.

This makes the form minimum size account for the content, while keeping
text selectability. It's not ideal because there's no caret / Ctrl+A
etc, but it's probably an ok trade-off? Alternatively we can wontfix /
make this depend on implementing field-sizing.

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

This doesn't change behavior, but it is more explicit.

Make the two resize code-paths invalidate the same way.

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

Bug 1911288 - Mark cross compartment edges from uncollected zones during gray marking that have been marked black since black marking happened (ESR128)  a=RyanVM

The problem here is that currently we mark incoming cross compartment edges
from uncollected compartments in two phases depending on the color of the
wrapper, but that color can change in between due to gray unmarking.

The patch does the simple thing of rescanning the incoming edges for black
wrappers after marking gray ones. This involves a little juggling of the
current mark color to ensure we can't mark black after marking gray.

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

Original Revision: https://phabricator.services.mozilla.com/D218719

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

Backed out 2 changesets (bug 1908095) for causing failures at browser_dbg-features-breakpoints.js. a=backout

Backed out changeset 21bf8880f772 (bug 1908095)
Backed out changeset 85060db8ce99 (bug 1908095)

Original Revision: https://phabricator.services.mozilla.com/D215639

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

It only make sense for touch input, as touch pointer ID always restarts from 0 while pen pointer ID always increments.

This won't work if there are multiple active pens, but that's rare enough and not straightforward to fix as somehow sActivePointersIds gets pointerId=0 instead of actual pointer ID for pens.

Original Revision: https://phabricator.services.mozilla.com/D214978

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

Bug 1911531 - Forbid any WorkerRunnable execution in WorkerPrivate::RunLoopNeverRan. r=dom-worker-reviewers,asuth a=RyanVM

This is a patch for uplift PreStartRunnable cleaning on the Worker thread for ESR128.
It includes the following fixes
[[ https://phabricator.services.mozilla.com/D213947 | bug 1894231 ]] introduces WorkerRunnable::mCleanPreStartDispatching instead of using WorkerPrivate raw pointer.
[[ https://phabricator.services.mozilla.com/D215601 | bug 1905337 ]] keeps dispatched PreStartRunnables in WorkerPrivate::mPreStartRunnables.
[[ https://phabricator.services.mozilla.com/D216379 | bug 1907383 ]] does not execute WorkerControlRunnable if Worker initialization fails
[[ https://phabricator.services.mozilla.com/D218619 | bug 1911531 ]] Ensures all dispatched runnables in Pending status are appended in WorkerPrivate::mPreStartRunnables.

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

Bug 1863246 - Make the page that enters BFCache not asking the parent process to update the active browsing context r=peterv,dom-core a=RyanVM

Currently, when a page enters BFCache, it updates the parent process
for the active BC; however, the page that is about to show will do the
same. These two operations are triggered in different processes with
different active id, they are racy and problematic.

This patch fixes the above issue by not updating the parent process
when a page enters BFCache.

This only applies to BFCacheInParent is enabled.

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

Bug 1908095 - [devtools] Regenerate debugger mochitest sourcemap resources r=devtools-reviewers,nchevobbe a=RyanVM

Depends on D218084

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

Bug 1908095 - [devtools] removeSessionDataEntry for webextension toolboxes and watcher targets r=ochameau,devtools-reviewers a=RyanVM

Fix removing breakpoints in webextension toolboxes and watcher targets, add tests to cover both scenarios

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

Http2 uses a single connection for multiple requests. When ORB blocks a
request with NS_ERROR_FAILURE, it's treated as a hard error in necko,
then the entire connection is closed.

This patches converts ORB to uses NS_BINDING_ABORTED.

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

The previous attempt at refining the subpixel anti-aliasing approximation modified the
distance-to-edge tracking, which can cause the AA to approach zero too soon.

This fixes this by reverting the distance-to-edge tracking back to the way it was, but
instead limiting the alpha to the area of the subpixel rectangle if necessary.

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

The existing distance-to-edge AA scheme breaks down somewhat when rectangles
have subpixel areas. We need to bias the AA to account for this situation when
the scales get to these subpixel sizes.

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

Disabling `MOZ_DATA_REPORTING` results in the `PREF_UPLOAD_ENABLED` pref not
being loaded with `Preferences.add`. This means
`Preferences.get(PREF_UPLOAD_ENABLED)` can possibly be `null`, which was
previously not handled and resulted in an error for the whole privacy.js file.

So only call `dataCollectionCheckboxHandler` for the `privateAttribution`
checkbox if `MOZ_DATA_REPORTING` is enabled (otherwise the `privateAttribution`
checkbox also just doesn't exist). Also move the call into separate
`initPrivateAttributionCheckbox` function to be more consistent with previous
code.

Original Revision: https://phabricator.services.mozilla.com/D218265

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

The general layout of the info pane is the same across platforms, so share the styles. This fixes the missing spacing on macOS after bug 1881256. Due to the changes in that bug, Windows no longer needs its own input styling, as it achieves the same appearance as the base styles (except for colors, which have been carried over).

Applied nesting to modified files.

Original Revision: https://phabricator.services.mozilla.com/D215464

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

After bug 1867854, dialog windows on macOS no longer show desktop tinting on the window background. Since this requires a transparent Gecko background, the `-moz-mac-unified-toolbar-window` appearance added in bug 1870481 should be applied to every window. It has been renamed to reflect this.

Original Revision: https://phabricator.services.mozilla.com/D215596

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

Rather than always hiding the titlebar for ToolbarWindows, conditionally show it if we are not drawing into it.

Original Revision: https://phabricator.services.mozilla.com/D215586

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

In bug 1668119, I adjusted macOS menupopups to only show a gutter if the menu contains either items that are checkboxes or radios, or checked/selected items of any type. However, this was not quite correct. In native macOS menus, a gutter is only shown if there is a checked/selected item--even if there are checkbox items, there should not be a gutter if no item is checked/selected. This patch matches that behavior.

Original Revision: https://phabricator.services.mozilla.com/D212217

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

GetURI can succeed, but still return null. In that case, BasePrincipal::IsL10nAllowed
will pass null into NS_URIChainHasFlags, causing it to fail, which will produce three
separate warnings, and then return NS_OK. A recent change caused this function to be
call much more frequently, so this is now the top source of log spam in debug builds.

This change should not affect the behavior, aside from the lack of warnings.

Original Revision: https://phabricator.services.mozilla.com/D219065

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

Bug 1909019 - [esr128] Use ParamTraits_TiedFields/_IsEnumCase in WebRenderMessageUtils instead of PlainOldDataSerializer. (complete) r=gw a=RyanVM

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

Bug 1909019 - [esr128] Use ParamTraits_TiedFields/_IsEnumCase in WebRenderMessageUtils instead of PlainOldDataSerializer. (partial) r=gw a=RyanVM

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

Original Revision: https://phabricator.services.mozilla.com/D216938

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

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

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

Bug 1898476 [Wayland] Lock Wayland surface before Swap buffers in RenderCompositorEGL r=emilio a=RyanVM

Depends on D214884

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

Depends on D214883

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

Bug 1898476 [Wayland] Move MozContainerSurfaceLock from MozContainerWayland to MozContainerSurfaceLock module r=emilio a=RyanVM

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

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

This default is used when the crash reporter has never been launched
before. Notably, this is currently a user-global setting (as opposed to
per-profile), so the defaults will typically only be used when someone
hasn't ever had Firefox installed on their system.

Original Revision: https://phabricator.services.mozilla.com/D218887

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

Ensures that all FullPageTranslationsPanel and SelectTranslationsPanel
instances will repopulate their dropdown menulist elements if the
application locale changes, to ensure that the language display names
are correct for the current locale.

Original Revision: https://phabricator.services.mozilla.com/D218682

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

Ensures that all FullPageTranslationsPanel and SelectTranslationsPanel
instances will repopulate their dropdown menulist elements if the
list of available languages changes, e.g. due to a Remote Settings sync.

Original Revision: https://phabricator.services.mozilla.com/D218681

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

Renames the TranslationsPanelShared.clearCache function to
clearLanguageListsCache to be more specific about what it does.

Original Revision: https://phabricator.services.mozilla.com/D218680

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