This also reorganizes things a bit in BackupService so that uninitBackupScheduler
also disarms the debouncer and any queued debounced jobs end up being inert.
Differential Revision: https://phabricator.services.mozilla.com/D218877
This is a BackupManifest schema change that will break recovering from
any backups created before this change. However, considering that we
haven't released this feature yet, I figured it wasn't worth the
effort of doing a schema version bump or handling of the prior
version.
I'm making the field optional in the BackupManifest because in the
event that we decide to backport the backup component to ESR 115,
we need to handle the fact that ESR 115 has no notion of a profile
group ID (and is unlikely to ever have such a notion).
Differential Revision: https://phabricator.services.mozilla.com/D218976
Bug 1915433 made this perma because it caused gfxPlatform initialization
(thus a bit more work), where before it used to be skipped by a pref.
But this happened intermittently before my patch, so likely this just
pushed the test over the limit...
Given the amount of tests skipped here on tsan, maybe we should have a
higher xpcshell timeout there?
Differential Revision: https://phabricator.services.mozilla.com/D221052
On dates like August 31st, in order to create a "Last Month" card, we should use a date near the *end* of the previous month - rather than the beginning - in order to avoid exceeding 60 days of history. (At some point, we can hopefully expand or remove that limit.)
Differential Revision: https://phabricator.services.mozilla.com/D220920
This is an infrastructure commit about adding a centralized place for tracking
the dependencies a compilation acquires as it is processed.
Differential Revision: https://phabricator.services.mozilla.com/D215565
With the changes done in [[ https://bugzilla.mozilla.org/show_bug.cgi?id=1911100 | 1911100 ]] Gela wanted to display the "Set as default browser" native prompt in home fragment.
The changes were backed out because addPrivateBrowsingShortcutFromHomeScreenCFRTest started to fail all of a sudden.
The UI test failed because the "Set as default browser" native prompt was displayed when performing the second switch to private browsing while trying to trigger the "Add private browsing shortcut" prompt.
To overcome this problem I've added a settings helper to disable it by default and use it where needed.
All UI tests successfully passed 3x on Firebase ✅
And I've also did a [[ https://firefox-ci-tc.services.mozilla.com/tasks/eMjCXxH1S2Kvmd3xdKYTNQ/runs/0/logs/public/logs/live.log | try run ]] with Gela's changes and addPrivateBrowsingShortcutFromHomeScreenCFRTest successfully passed 50x on Firebase ✅ (after landing these changes she can try to land her changes again)
Differential Revision: https://phabricator.services.mozilla.com/D221038
Besides porting helper_fission_inactivescroller_under_oopif, this adds
helper_fission_utils.js::hitTestOOPIF() which will replace
helper_fission_utils.js::fissionHitTest(). The latter will be removed
with the completion of Bug 1841896.
Differential Revision: https://phabricator.services.mozilla.com/D217165
We keep information about the PipeWire camera status as a member of the
PipeWire session, but it's never updated and remains in uninitialized
state. Make sure it gets updated once PipeWire is initialized or when it
fails. There is currently no use for this member variable, but there is
a plan to use it so I'm rather keeping it instead of removing it.
This is a simple backport of an WebRTC upstream change.
Upstream commit: 3881cb65cfcec90b6f0a56ce7223a471aa0115f2
Differential Revision: https://phabricator.services.mozilla.com/D220895
We have to always update camera availability information, even when we
don't request cameras, because the WebRTC backend automatically creates
camera video engine and not having this information we might hitting an
assert later, where we assume the status of camera availability is not
unknown.
Differential Revision: https://phabricator.services.mozilla.com/D219062
lougeniac64