Bug 1627220 - Consider quota manager activity for cookie purging. r=ewright We're using nsIStorageActivityService to get only principals that were using storage in the last 3 days. A few notes on that: - 3 days is based on the assumption that it's very unlikely that a client would miss idle daily for 3 days in a row. - We're currently only persisting activity for up to 24 hours. Bug 1630598 tracks extension to 3 days. - We're currently not persisting storage activity service across restarts. This is bug 1459974 which we're aiming to resolve. - This will not immediately clear all old tracking storage, only when it is used another time. In the same vein there's a chance the we miss clearing if the user manages to persistently have Firefox sessions that are so short that idle-daily is rarely triggered. This would be problematic for cookie purging in general, though. - This produces a significantly lower number of principals to check. We could consider switching cookies to the same approach (only get the last x days of activity). I talked to Steve Englehardt and we're generally okay with these caveats in favor of the simplified implementation. Differential Revision: https://phabricator.services.mozilla.com/D71173

Bug 1597267 - Remove dom.registerProtocolHandler.insecure.enabled r=annevk,emilio Differential Revision: https://phabricator.services.mozilla.com/D69400

Bug 1629843 - Mark indexedDB classes as able to have pointers into more than one JS zone r=mccr8 Differential Revision: https://phabricator.services.mozilla.com/D71289

Bug 1629735 - Implement parsing / selector-matching for :is() and :where(). r=heycam This implements the easy / straight-forward parts of the :where / :is selectors. The biggest missing piece is to handle properly invalidation when there are combinators present inside the :where. That's the hard part of this, actually. But this is probably worth landing in the interim. This fixes some of the visitors that were easy to fix. Differential Revision: https://phabricator.services.mozilla.com/D70788

Bug 1629680 - When determining the original default engine, fallback to the configuration set engine if the cached engine can't be found. r=daleharvey This helps fix the case when language switching that we get the wrong default engine if the cache is out of date. Modern is unaffected as it doesn't use ABSearch, but the test covers both to make sure. Differential Revision: https://phabricator.services.mozilla.com/D71216

Bug 1630708 - Rename bugbug_push_schedules shadow scheduler to bugbug_all for consistency. r=ahal Depends on D71205 Differential Revision: https://phabricator.services.mozilla.com/D71327

Bug 1630708 - Increase the confidence thresholds used by the bugbug-based strategies. r=ahal Keeping the same for the currently chosen strategy for try auto, since we don't want to decrease its regression detection rate. We also add a new shadow scheduler which uses the reduced set with a higher confidence threshold. Differential Revision: https://phabricator.services.mozilla.com/D71205

Backed out 4 changesets (bug 1624268) for causing brwoser-chrome failure at toolkit/components/antitracking/test/browser/browser_partitionedSharedWorkers.js CLOSED TREE Backed out changeset d58da2438eee (bug 1624268) Backed out changeset 06adb66489b8 (bug 1624268) Backed out changeset c947c72829a6 (bug 1624268) Backed out changeset 8af99a5ecd54 (bug 1624268)

Bug 1627739 - Do not delay FrameTexturesUpdated notifications for empty updates. r=kvark The FrameTexturesUpdated event is intended to be issued when any necessary texture cache updates have been completed for the current frame. Originally we would simply check if the pending_texture_updates vector in Renderer is empty. However the updates themselves could be nops, and not trigger a timely frame render to occur, causing the notifications to be delayed indefinitely. Now we track if there are actually any pending specifically texture cache updates and only defer the notification if true. A consequence of deferring the notification indefinitely was revealed when animating images just outside the current view. We would not release the buffers for recycling even though we had no reason to hold onto them. This could cause the image decoder to allocate new buffers while the old buffers would not get released. It was not a true memory leak because as soon as a frame is rendered, it would release all of the old buffers, but it could easily cause a out of memory crash to occur if the user was not interacting with the browser while in this state. Differential Revision: https://phabricator.services.mozilla.com/D70770

Bug 1627206 - Upgrade failure telemetry for HTTPS Only Mode. r=ckerschb,jcj,dragana Differential Revision: https://phabricator.services.mozilla.com/D69983

Bug 1630629. Block WebRender on Intel if no DComp. r=aosmond This moves the DirectComposition configuration code before the WebRender configuration code so that we can depend on the results to decide whether to user WebRender. Differential Revision: https://phabricator.services.mozilla.com/D71213

Bug 1629832 - add tooltips to all the window control buttons, r=dao,fluent-reviewers,flod Differential Revision: https://phabricator.services.mozilla.com/D71199

Backed out 2 changesets (bug 1625500) for multiple failures on a CLOSED TREE Backed out changeset 7d80233bcfcd (bug 1625500) Backed out changeset 0a35b13dfcde (bug 1625500)

Bug 1605209 - Turn actor names into nsCString;r=nika This should save (a little) memory and avoid quite a few conversions. Differential Revision: https://phabricator.services.mozilla.com/D70341

Bug 1605209 - Extending BrowserTestUtils to allow out-of-stack crashing;r=mconley Differential Revision: https://phabricator.services.mozilla.com/D70191

Bug 1605209 - Testing JSWindowActor crash annotations;r=gsvelto Differential Revision: https://phabricator.services.mozilla.com/D70175

Bug 1605209 - Annotate JSWindowActor's message exchanges to determine which actor is on the stack of a crash;r=gsvelto,nika Differential Revision: https://phabricator.services.mozilla.com/D69993

Bug 1624268 - Part 4: Remove unnecessary code for ContentBlocking::ShouldAllowAccessFor(). r=dimi,baku As we change to use the 'HasStoragePermission' flag, there are some code became uncessary. This patch removes those code. Differential Revision: https://phabricator.services.mozilla.com/D71034

Bug 1624268 - Part 3: Use the 'HasStoragePermission' flag to check the storage permission. r=dimi,baku We move to use the 'HasStoragePermission' flag to check the storage permission. For the storage permission check of windows, the flag would come from the WindowContext. For the check of channels, the flag would come from the loadInfo of the channel. Differential Revision: https://phabricator.services.mozilla.com/D71033

Bug 1624268 - Part 2: Moving the setting of 'HasStoragePermission' flag to the WindowContext a bit earlier. r=dimi,baku We need the 'hasStoragePermission' flag for calculating the HasStorageAccess() value. Right now the setting of the flag is later than the calculation. So, we move the setting before the calculation. Differential Revision: https://phabricator.services.mozilla.com/D71032