Marco Simonelli authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

- fixes required to build dom/media/systemservices

Marco Simonelli authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

- fixes required to build dom/media/webrtc

Marco Simonelli authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

- fixes requried to build netwerk/sctp

Marco Simonelli authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

- fixes required to build third_party/sipcc

Marco Simonelli authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

- fixes required to build third_party/libwebrtc

Marco Simonelli authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

- properly define NOMINMAX for just MSVC builds

henry authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

Remove this patch after upstream bugzilla bug 1790187

henry authored 2 years ago and Pier Angelo Vendrame committed 6 months ago

Temporary fix until mozilla bug 1799153 gets a patch upstream.

ma1 authored 7 months ago and Pier Angelo Vendrame committed 6 months ago

Bug 43005: followup, fix backporting conflict.

Arturo Mejia authored 7 months ago and Pier Angelo Vendrame committed 6 months ago

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

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

Jon Coppeard authored 8 months ago and Pier Angelo Vendrame committed 6 months ago

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

Timothy Nikkel authored 9 months ago and Pier Angelo Vendrame committed 6 months ago

Bug 1899180. If a channel is not nsIPrivateBrowsingChannel and has no load context, use the private browsing field from it's origin attributes. r=necko-reviewers,anti-tracking-reviewers,valentin

If the channel is not a nsIPrivateBrowsingChannel, and it also has no load context (eg inside svg images) then we will over write a non-zero mPrivateBrowsingId on the OriginAttributes of the channel with 0, making NS_UsePrivateBrowsing return false for the channel.

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

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

This was created by reverting revs 5b6b822f52e6+9bac10b90db8 then
re-grafting revs 5f911e4787cb+4e9fe79abfdf and folding the resulting
commits together.

Bug 1906744 - Check if constructor is enabled before installing named property. r=mccr8,dom-storage-reviewers,janv,asuth,eemeli a=RyanVM

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

There's no sufficiently robust way to identify POD types in C++, such
that we could rely on this kind of thing for serialization.

As one example, `bool` must be carefully handled on deserialize, in case
an attacker wants to exploit the UB of bool with value 2.
Additionally, generally it's not viable to tell whether all the members
of a struct are PODs as well, and we need that level of assurance
recursively!

So we instead lean on e.g. ParamTraits_TiedFields/_IsEnumCase for our
extreme robustness requirements.

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

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

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

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

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

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

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

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

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

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

The reftest here currently fails on Android for what appears to be an
unrelated reason: reftest-analyzer shows that in the *reference* case,
all but the last line of text is completely missing.

I'm not sure what's failing there (but it fails similarly without this
patch, anyhow); we should investigate that as a separate bug.

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

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

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

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

Bug 1902253 - When the compositing mode is not OVER, we must first render the color glyph to a temporary surface, then composite it with the appropriate operator. r=lsalzman a=RyanVM

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

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

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