Backed out changeset 6c542cd8d622 for causing devtools compat issues. CLOSED TREE

Backed out changeset 1b43d3f38946 (bug 1777209) for causing reftest failures e.g. 602200-4.html. CLOSED TREE

Bug 1702806 - Fix issues with intermittient failures in places tests and due to the way the dialogs interact with PlacesTransactions. r=mak There's are a couple of issues that this fixes, they are both based around the issue that because tests run fast they tend to not give time for batches to complete. This can lead to incomplete batches between tests, which tends to mess up subsequent tests or cause hangs. In normal usage this is not an issue, as the user is not able to go as fast as tests. The first issue is that in PlacesUIUtils.showBookmarkDialog we may resolve the dialog deferred promise before the transaction batch has had change to complete. The second issue is that the star UI runs batches, and that again we do not wait for the batch to be complete. Working an await into the star UI/tests is more difficult due to the way that code is structured. With a planned switch to non-instant apply, it also feels too complicated to be worth it at this time. As a workaround for this issue, we ensure that the transaction queue is cleared between each test run via a registerCleanupFunction in the head.js file. Differential Revision: https://phabricator.services.mozilla.com/D147535

Bug 1776832 - Clear chrome module environments in shutdown r=arai Differential Revision: https://phabricator.services.mozilla.com/D150966

Bug 1777209 - Use DrawSurface rather than FillRect to paint <canvas>, and don't use EXTEND_PAD when writing to PDF. r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D150601

Bug 1774458 - Use undocumented, non-public adaptive spinlocks on macOS 10.15+, revert to user-space spinlocks on older versions r=pbone Differential Revision: https://phabricator.services.mozilla.com/D149599

No Bug, mozilla-central repo-update HSTS HPKP remote-settings tld-suffixes - a=repo-update r=diannaS Differential Revision: https://phabricator.services.mozilla.com/D150961

Bug 1776145 - [devtools] Remove WebConsoleConnectionProxy. r=ochameau. Differential Revision: https://phabricator.services.mozilla.com/D150087

Bug 1776145 - [devtools] Remove unnecessary WebConsoleUI additionalProxies. r=ochameau,devtools-backward-compat-reviewers,jdescottes. `WebConsoleConnectionProxy` is now only used for: - listening to `lastPrivateContextExited`, which can be done from the top-level console front instead - setting `NetworkMonitor.saveRequestAndResponseBodies` for toolbox we don't have network resource support for, which would be better done in `startWatchingNetworkResources`. This means we don't need to keep a Map of additional proxies. The only impact is on `clearMessagesCache`, where we now fetch all fronts with `getAllFronts` instead of looping through the Map of additional proxies. This change highlighted some race condition in tests, as it's now slightly slower. So we add a new `clearMessagesCacheAsync` function, which is doing the same thing as `clearMessagesCache`, except it's not `oneway`, so we can know when the cache was indeed cleared, and we emit an event to indicate when the cache was cleared. We can't simply remove `oneway` from `clearMessagesCache` as it causes backward compatibility issues we can't avoid. This also highlighted an issue with the cache not being cleared on `console.clear` when it is batched, so we fix this (a test was failing without it). The next patch in the queue will completely remove `WebConsoleConnectionProxy`. Differential Revision: https://phabricator.services.mozilla.com/D150085

Bug 1773696 - Make wheel event IPC depend on test_events_async_enabled, r=smaug The `widget->DispatchInputEvent` codepath only works in gecko CI configurations, so to allow this to be used for e.g. WebDriver implement a path that doesn't go via the parent process. Differential Revision: https://phabricator.services.mozilla.com/D150632

Backed out changeset 22c5f55e75c2 (bug 1777517) for causing build bustages on Unified_cpp_widget_windows2.obj CLOSED TREE

Bug 1777517 - [Cocoa] Add clipboard logs; r=NeilDeakin Differential Revision: https://phabricator.services.mozilla.com/D150790

Bug 1777914 - IDBTransaction::AbortInternal doesn't send the abort message when needed; r=dom-storage-reviewers,jstutte Transactions transition to the finished state in following cases: 1. No requests have been created and we are back at the event loop. 2. The last request has been finished. 3. A transaction has been explicitly aborted. 4. A transaction has been explicitly committed. When a transaction is finished, we send either an abort or commit message to the parent process. Bug 1598164 introduced an active and inactive state, so the state can't be used for determining if a request was created. However, this was initially overlooked, so we ended up not sending the abort message in some cases which led to intermittent failures. The correct wasy to determine if the abort messages should be sent to the parent process is to check mStarted flag only. Differential Revision: https://phabricator.services.mozilla.com/D150937

Bug 1770019 - Make httpd.js support both IPv4 and IPv6, r=necko-reviewers,dragana Differential Revision: https://phabricator.services.mozilla.com/D148696

Bug 1777694 - Cache the result of JSM to ESM fallback in the shim. r=jonco Differential Revision: https://phabricator.services.mozilla.com/D150874

Bug 1777829 - Fix DevTools stub generator. r=devtools-reviewers,nchevobbe Differential Revision: https://phabricator.services.mozilla.com/D150885

Bug 1750972 - Remove same-site schemeful and noneRequiresSecure experimental features. r=preferences-reviewers,Gijs Differential Revision: https://phabricator.services.mozilla.com/D150604

Bug 1750972 - Remove tests setting noneRequiresSecure = true. r=freddyb Differential Revision: https://phabricator.services.mozilla.com/D150603

Bug 1750972 - Enable same-site schemeful and noneRequiresSecure by default. r=freddyb Depends on D150600 Differential Revision: https://phabricator.services.mozilla.com/D150602

Bug 1777901 - Pt 2 - Port more wrench tests to specify clips via clip-chains r=gfx-reviewers,lsalzman Differential Revision: https://phabricator.services.mozilla.com/D150927

Bug 1777901 - Port more wrench tests to specify clips via clip-chains r=gfx-reviewers,lsalzman The intent is to deprecate specifying clips via ClipId::Clip(..) as this will simplify the ongoing clip-interning work. Differential Revision: https://phabricator.services.mozilla.com/D150925

Bug 1777924 - [devtools] Use legacy wrapper in update_remote_settings_records.mjs for forward compatibility with Node 16+ r=nchevobbe Differential Revision: https://phabricator.services.mozilla.com/D150939

Merge mozilla-central to autoland. CLOSED TREE

Merge autoland to mozilla-central. a=merge

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD bn -> 48e59454a734b72290b4cf280e6e66e4d0c069fa dsb -> 2971738372d2acdcc3650a9dc4d4f120cdedf940 es-CL -> aa2c4e0a39c2bc090a4e469f1ff915f644b6af30 it -> f544bcbf9850cd478cffde827b3e0eace2cd646b mk -> 6db6197027b62126eb7aaec789f82fed5ad35afd pt-BR -> dcc404ec36a8184473c5b0a5f3d2431f306f2de1 uk -> adc076493d0a38cb619af6168aa1e904e1a76c27

Bug 1777929 - Update an l10n string id after a change r=flod Differential Revision: https://phabricator.services.mozilla.com/D150941

Bug 1754932 - LUL initialisation: replace `CallFrameInfo::Rule` and 7 children with a fixed-sized structure. r=mstange. At profiler startup, LUL reads and preprocesses Dwarf unwind info for all shared objects mapped into the process. That includes libxul.so and around 90 other shared objects on an x86_64-linux build. This takes too long. Profiling just this reading phase shows a huge number of mallocs and frees resulting from LulDwarf.cpp. The largest cause of these is the implementation of a sum-of-products type with 7 variants (CallFrameInfo::*Rule) using C++ inheritance. The variants have different sizes and so have to be boxed (stored on the heap and referred to by pointers). They are very short lived and this causes a lot of heap turnover. For an m-c build on x86_64-linux on Fedora 35 using clang-13.0.0 -g -O2, when measuring a MOZ_PROFILER_STARTUP=1 run that is hacked so as to exit immediately after the unwind info for libxul.so has been read, this patch has the following perf effects: * run time reduced from 0.50user to 0.41user (Core i5 1135G7, circa 4 GHz) * heap allocation reduced from 8,087,404 allocs/397,177,435 bytes to 3,176,936 allocs, 328,204,042 bytes. * instruction count reduced from 6,848,730,307 to 5,572,028,393. Main changes are: * `class CallFrameInfo::Rule` has been completely rewritten, so as to merge its 7 children into it, and those children have been removed. The new representation uses just 3 machine words to represent all 7 alternatives. The various virtual methods of `class CallFrameInfo::Rule` (`Handle`, `operator==`, etc) have been rewritten to use a simple switch-based scheme. * The code that uses `class CallFrameInfo::Rule` has been changed (but not majorly rewritten) so as to pass around instances of it by value, rather than pointers to it. This removes the need to allocate them on the heap. To simulate the previous use case where a NULL value had a meaning, the revised class in fact has an 8th alternative, `INVALID`, and a routine `isVALID`. INVALID rules are now used in place of NULL pointers to rules as previously. * Accessors and constructors for the revised `class CallFrameInfo::Rule` hide the underlying 3-word representation, ensure that the correct representational invariants are maintained, and make it impossible to access fields that are meaningless for the given variant. So it's not any less safe than the original. * Additionally, Dwarf expression strings are no longer represented using `std::string`. Instead a new two-word type `ImageSlice` has been provided. This avoids all unnecessary (and unknown) overheads with `std::string` and provides a significant part of the measured speedup. Differential Revision: https://phabricator.services.mozilla.com/D139288

Bug 1777357 - [wpt-sync] Update web-platform-tests to 57483c9910074efb2cfa6d41dbed261b81d3bede, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 57483c9910074efb2cfa6d41dbed261b81d3bede wpt-type: landing

Bug 1777194 [wpt PR 34643] - Update wpt metadata, a=testonly wpt-pr: 34643 wpt-type: metadata

Bug 1777194 [wpt PR 34643] - [@container] Clear results according to ContainerQueryEvaluator::Change, a=testonly Automatic update from web-platform-tests [@container] Clear results according to ContainerQueryEvaluator::Change In ContainerQueryEvaluator::ContainerChanged, we currently clear *all* results whenever we compute any Change other than kNone. However, for computed change=kNearestContainer it is not correct to clear results with change=kDescendantContainers, since in that situation we're not going to recalculate the container-query-dependent elements within nested containers, hence all the results aren't repopulated. This causes us to miss invalidation in some cases. Fixed by only clearing results less than or equal to the computed change. Also added additional assertions and comments to the test ContainerQueryEvaluatorTest.ContainerChanged. That change was prompted by the slightly unclear/inaccurate comment about results being cleared whenever ContainerChanged is called. It's better to be explicit about what we expect the results to be. Fixed: 1340351 Change-Id: I64467104b6b0eacef5100d67f6b8f8287a57d0a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3732493 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/main@{#1019074} -- wpt-commits: 57483c9910074efb2cfa6d41dbed261b81d3bede wpt-pr: 34643

Bug 1776786 [wpt PR 34619] - Allow NG fragment traversal inside SVG in multicol., a=testonly Automatic update from web-platform-tests Allow NG fragment traversal inside SVG in multicol. TLDR; remove obsolete and somewhat harmful code. The code that checked whether it was ok to do fragment traversal of an object inside multicol incorrectly refused fragment traversal inside SVG, for no good reason. If we're inside a flow thread, the correct way to check would be to keep walking up the tree until we either find an NG object, or a legacy object that was *forced* to do legacy fallback, and ask *that* object - not its immediate parent. The way it was, we would stop at LayoutSVGRoot and just say no to fragment traversal. But LayoutSVGRoot doesn't have an NG counterpart. It's fine to walk past legacy objects, as long as they aren't forced to be legacy objects, so that we can tell whether our ancestry consists of glorious traversable NG objects or not. However, this code is no longer needed, since we now always refuse NG objects inside forced legacy fallback anyway, as of CL:3461697. So just remove the code instead. Bug: 1339391 Change-Id: I9ef55e551ed86fb5b5843108526c58e393a617e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3726352 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#1019068} -- wpt-commits: bb66b98321db60735132cb0b8d88587477a0fd37 wpt-pr: 34619

Bug 1777124 [wpt PR 34637] - WhitespaceChildrenMayChange needs to be handled for all elements, a=testonly Automatic update from web-platform-tests WhitespaceChildrenMayChange needs to be handled for all elements We tried to optimize away WhitespaceChildrenMayChange handling for subtrees which should regardlessly be re-attached, but descendants further down could still be marked for re-attachment which caused us to stop early for ancestor marking at those whitespace-marked elements. Remove the ReattachLayoutTree() check and handle the whitespace flag if there is a LayoutObject. Bug: 1338779 Change-Id: Iad95fdd674ca679137e66d5d4394efda0a8a4571 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3732708 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1019057} -- wpt-commits: 67953c9f5612c4328e206f46d9929d927ff0c299 wpt-pr: 34637

Bug 1776709 [wpt PR 34606] - Add regression test for document.baseURI., a=testonly Automatic update from web-platform-tests Add regression test for document.baseURI. The `document.baseURI` is wrongly implemented in Chrome for about:blank and about:srcdoc. It allows leaking cross-origin data. The leak happens only when the two origin are hosted by the same process. This patch adds regression tests. I am going to mitigate this bug in a follow-up. Bug: 1336904 Change-Id: I027249095fc7ba55dc3f68c772a72f473cfec409 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3723568 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/main@{#1019052} -- wpt-commits: d32fb934a67634928c99760e66ac1cc1e2253e2c wpt-pr: 34606

Bug 1776286 [wpt PR 34565] - [css-pseudo] Implement ::marker text as a LayoutTextFragment, a=testonly Automatic update from web-platform-tests [css-pseudo] Implement ::marker text as a LayoutTextFragment The text of a ::marker with 'content: normal' used to be a LayoutText. This prevented it from being updated when dynamically changing the 'text-transform' of the ::marker. Using LayoutTextFragment aligns the behavior with the non-normal case and solves the problem. Fixed: 1338708 TEST=external/wpt/css/css-pseudo/marker-text-transform-dynamic.html Change-Id: Ie50e46f1de00f87b3aa83e3c464085d7f4860bc3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3719019 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018836} -- wpt-commits: 3a9bbb0b1c0eacff5033850d32b924a80bc10f6e wpt-pr: 34565

Bug 1776873 [wpt PR 34625] - Update wpt metadata, a=testonly wpt-pr: 34625 wpt-type: metadata

Bug 1776873 [wpt PR 34625] - [@container] Invalidate container-relative units in @container prelude, a=testonly Automatic update from web-platform-tests [@container] Invalidate container-relative units in @container prelude The internal CSSContainerValues of a ContainerQueryEvaluator as of recently contains a CSSToLengthConversionData::ContainerSizes object which caches the values used for resolving container-relative units. This cache needs to be invalidated, otherwise affected queries will not be responsive to changes. This is roughly the same problem as the 'rem' unit invalidation that was fixed recently, so we can generalize that to solve the current problem. Note that this CL removes font_dirty_=true that previously took place in RootFontChanged. This flag doesn't fit anymore with the generalization (UpdateValuesIfNeeded), but it's also actually not needed for the 'rem' unit case, since we anyway recalculate the style of all descendants. Fixed: 1340232 Change-Id: I7acfb475d1b7d08c84fdf09b7fb0be6b608d0c26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3731812 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018817} -- wpt-commits: 2f9a2a84ac665f1a8ab1fe722902b5fe61bfdf47 wpt-pr: 34625

Bug 1776860 [wpt PR 34624] - Need post-layout fragments on fragment item cache hit., a=testonly Automatic update from web-platform-tests Need post-layout fragments on fragment item cache hit. We previously used to always get post-layout fragments when cloning a fragment item, but CL:3677013 changed that, since it's no longer a given that we always do want the post-layout fragments, and that the callers rather fetch the post-layout fragments at their own discretion. Back when I wrote that CL, I didn't realize that NGFragmentItemsBuilder::AddPreviousItems() relied on getting post-layout fragments as well (probably because cs.chromium.org failed to list all call sites to NGFragmentItemsBuilder::ItemWithOffset::ItemWithOffset()). Bug: 1340168 Change-Id: I5f799aa5305c7588d7a6034b2f8eab33b8e1a89c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3731811 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018694} -- wpt-commits: dfb10692e649e537946ef5db98898649c9010d98 wpt-pr: 34624

Bug 1776258 [wpt PR 34561] - Update wpt metadata, a=testonly wpt-pr: 34561 wpt-type: metadata

Bug 1776258 [wpt PR 34561] - Allow hide animations to be started from pop up hide event, a=testonly Automatic update from web-platform-tests Allow hide animations to be started from pop up hide event See [1] for the origin of this change, which makes it possible to trigger pop up hide animations from within the `hide` event handler. For example: popup.addEventListener('hide', () => { popup.animate({ transform: 'translateY(-50px)', opacity: 0, }, 200); }); To accomplish that, the hide process now looks like this: 1. Capture any already-running animations via getAnimations(), including animations on descendent elements. 2. Remove the :top-layer pseudo class. 3. Fire the 'hide' event. 4. If the hidePopup() call is *not* the result of the pop-up being "forced out" of the top layer, e.g. by a modal dialog or fullscreen element: a. Restore focus to the previously-focused element. b. Update style. (Animations/transitions start here.) c. Call getAnimations() again, remove any from step #1, and then wait until all of them finish or are cancelled. 5. Remove the pop-up from the top layer, and add the UA display:none style. 6. Update style. [1] https://chromium-review.googlesource.com/c/chromium/src/+/3688871/9/third_party/blink/renderer/core/dom/element.cc#2660 Bug: 1307772 Change-Id: I910535b13cfc3c8f8498ed64dae73caa75dd7317 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3708419 Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Commit-Queue: Robert Flack <flackr@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018685} -- wpt-commits: d4a7c77961af00b9a4ba78b0f80d771a519f78c6 wpt-pr: 34561

Bug 1776680 [wpt PR 34603] - Update wpt metadata, a=testonly wpt-pr: 34603 wpt-type: metadata

Bug 1776680 [wpt PR 34603] - [@container] Test invalidation of font-relative units separately, a=testonly Automatic update from web-platform-tests [@container] Test invalidation of font-relative units separately This WPT changed both the root font and non-root font at the same, which means one invalidation mechanism may overlap. Test each unit separately instead. Bug: 1339808 Change-Id: I18fcef9f92358c437bb5c547132f8a5348c0d39f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3726452 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018645} -- wpt-commits: a19cb86d9e1fce816ddd8f2055d9c60ac6119fdc wpt-pr: 34603

Bug 1774167 [wpt PR 34424] - Update wpt metadata, a=testonly wpt-pr: 34424 wpt-type: metadata

Bug 1774167 [wpt PR 34424] - fetch: Add Set-Cookie as an invalid request header, a=testonly Automatic update from web-platform-tests Fetch: add Set-Cookie as an invalid request header See https://github.com/whatwg/fetch/pull/1453 for context. -- wpt-commits: 5fb9aee1a0d59531dbe4be9300d4036e00ba2eb5 wpt-pr: 34424

Bug 1776845 [wpt PR 34621] - Update wpt metadata, a=testonly wpt-pr: 34621 wpt-type: metadata

Bug 1776845 [wpt PR 34621] - [@container] Fix @media crash for custom properties, a=testonly Automatic update from web-platform-tests [@container] Fix @media crash for custom properties style() container queries accidentally allowed evaluating custom property evaluation for media queries causing a crash with a null ComputedStyle. Bug: 1340185, 1339962 Change-Id: I8d8529272392e0ed0c5ef4e6d369f2676fe5ee71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3726078 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018639} -- wpt-commits: 8b629e867b7564c0e4277db121de53fa3aeae7bd wpt-pr: 34621

Bug 1770441 [wpt PR 34145] - Add support for PAC (per-test proxy configuration), a=testonly Automatic update from web-platform-tests Add support for PAC (per-test proxy configuration) (#34145) Tests can now delcare that they use a PAC file (Proxy Auto-Configuration, see https://developer.mozilla.org/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file) The syntax: `<meta name="pac" content="relative/url/to/pac-file.js">` See RFC112 -- wpt-commits: ddeae538bbc9d634c983238fceea89ff08d00a86 wpt-pr: 34145

Bug 1775537 [wpt PR 34536] - Update wpt metadata, a=testonly wpt-pr: 34536 wpt-type: metadata

Bug 1775537 [wpt PR 34536] - Rename CanvasFilter WPTs to be tentative, a=testonly Automatic update from web-platform-tests Rename CanvasFilter WPTs to be tentative The spec is being reverted per https://github.com/whatwg/html/pull/7874 due to lack of multi-implementer interest. So, we need to rename the tests. Bug: 1169216 Change-Id: I059fa4c951f2076cffb562bf4a32d4e4284d3771 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3714402 Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Commit-Queue: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018614} -- wpt-commits: 0c579dc895666e989c046b706955ca19d1244c7d wpt-pr: 34536

Bug 1775405 [wpt PR 34519] - Resolve FIXME in LayoutQuote by using English quotes as default, a=testonly Automatic update from web-platform-tests Resolve FIXME in LayoutQuote by using English quotes as default Legacy FIXME in layout_quote.cc to change default "quote" (%22) to English “quote” (%E2%80%9C, %E2%80%9D). Fixed all affected tests. Change-Id: I0dcff0d2356ccbf53ebb16e3ad8abe930f410a50 Bug: 753671 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3704099 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018608} -- wpt-commits: 0b8d6e703759e62ee7439687d88144a46b881d66 wpt-pr: 34519

Bug 1776410 [wpt PR 34577] - `await_promise` is mandatory, a=testonly Automatic update from web-platform-tests `await_promise` is mandatory (#34577) Make `script.evaluate`->`awaitPromise` mandatory. Co-authored-by: Maksim Sadym <sadym@google.com> -- wpt-commits: a59332b7317247a99cfa75d9fa79e0816f5fbcfe wpt-pr: 34577

Bug 1774098 [wpt PR 34412] - Bump types-six from 1.16.15 to 1.16.16 in /tools, a=testonly Automatic update from web-platform-tests Bump types-six from 1.16.15 to 1.16.16 in /tools Bumps [types-six](https://github.com/python/typeshed) from 1.16.15 to 1.16.16. - [Release notes](https://github.com/python/typeshed/releases) - [Commits](https://github.com/python/typeshed/commits) --- updated-dependencies: - dependency-name: types-six dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> -- wpt-commits: c422ad60d4f047bd11df1f593e23bb53bc737447 wpt-pr: 34412

Bug 1770651 - Make sure tabs.update don't use loadURI on a discarded tab. r=mixedpuppy Differential Revision: https://phabricator.services.mozilla.com/D149702

Bug 1727753 - [devtools] Ogg file request is not displayed in Network Monitor when media switch is selected r=Honza Differential Revision: https://phabricator.services.mozilla.com/D150072

Bug 1777222 part 5 - Add a small cache to optimize NewPlainObjectWithProperties. r=jonco With TI we had a cache for this but we got rid of it when we removed TI. This patch adds back a simpler version of it that caches the four most recently created shapes. This cache has a good hit rate on the web and on Kraken's json-parse-financial test. Differential Revision: https://phabricator.services.mozilla.com/D150558

Bug 1777222 part 4 - Use templates to optimize the unique-names case better. r=jonco If the caller knows there are no duplicate or integer keys, we don't need to check for these cases. Differential Revision: https://phabricator.services.mozilla.com/D150557

Bug 1777222 part 3 - Remove NewObjectKind argument. r=jonco Differential Revision: https://phabricator.services.mozilla.com/D150556

Bug 1777222 part 2 - Avoid calling NativeDefineDataProperty in the common case. r=jonco Differential Revision: https://phabricator.services.mozilla.com/D150555

Bug 1777222 part 1 - Inline AddPlainObjectProperties into NewPlainObjectWithProperties. r=jonco Differential Revision: https://phabricator.services.mozilla.com/D150554

Bug 1777790 - Fixed typo "PATH" to "PATCH" in http custom request panel drop down list. r=bomsy Differential Revision: https://phabricator.services.mozilla.com/D150886

Bug 1583910 - New inactive CSS rule to show warning when border-image is made inactive by border-collapse. r=nchevobbe,fluent-reviewers,flod Differential Revision: https://phabricator.services.mozilla.com/D147205

Bug 1775150 - Cleanup js/xpconnect includes r=sylvestre Differential Revision: https://phabricator.services.mozilla.com/D149803

Bug 1767684 - [devtools] Skip browser_rules_cycle-angle.js on linux r=devtools-reviewers,nchevobbe I checked that skipping the test does not move the intermittent to the next test. I am not sure what makes this test problematic, I suppose this has to do with initializing widgets in the inspector to handler filters. Let's skip this on linux for now. Differential Revision: https://phabricator.services.mozilla.com/D150859

Bug 1767260 - [wdspec] Add tests for context in log.entryAdded event. r=webdriver-reviewers,jdescottes Depends on D150406 Differential Revision: https://phabricator.services.mozilla.com/D150559

Bug 1767260 - [wdspec] Format tests for log.entryAdded event. r=webdriver-reviewers,jdescottes Depends on D150405 Differential Revision: https://phabricator.services.mozilla.com/D150406

Bug 1767260 - [bidi] Add support for source to log.entryAdded event. r=webdriver-reviewers,jdescottes,whimboo Depends on D150107 Differential Revision: https://phabricator.services.mozilla.com/D150405

Bug 1775463 - Allow windowglobal-in-root modules to intercept events from their corresponding windowglobal module. r=webdriver-reviewers,jdescottes Differential Revision: https://phabricator.services.mozilla.com/D150107

Merge mozilla-central to autoland CLOSED TREE

Merge autoland to mozilla-central a=merge

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD de -> 7e0a17ca783667e7514b5e13097f14a414a581dd ko -> 422482b1d9efcd9132f7d1c155378f0fad13a25a pt-BR -> 564c5d512059fd8bc597f66193241084f6b112c9 tg -> fe59cfc0c58d352d10fd3f82fe90c54a49122350 uk -> d77a7d270d57167a98f03116455dc50c3f896ffc

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD id -> 59fc812433a65f89acca5fd3d0b88885f2e0f7a1 ru -> f18dc88bad3435125ed914d1d6187eff10b14e46 tg -> 1b3ba16a0eca5b0ad55943e3bf5402c84cd211b5 uk -> d4a2520820de007c52009ff994289fe6fdb441cf

Bug 1770461 - [wdspec] Test various return values for script.evaluate awaitPromise r=webdriver-reviewers,whimboo Depends on D149412 Differential Revision: https://phabricator.services.mozilla.com/D149924

Bug 1770461 - [bidi] Add support for awaitPromise to script.evaluate r=webdriver-reviewers,whimboo,jgraham Differential Revision: https://phabricator.services.mozilla.com/D149412

Bug 1682621, the command event can supply an input source so provide it in PendingPopup::MouseInputSource so that it is available during the popupshowing event, r=tnikkel This is to fix the test failure in browser_menu_touch.js. Differential Revision: https://phabricator.services.mozilla.com/D150805

Bug 1682621, remove keypress listener for main toolbar buttons, and use the inputSource to distinguish keyboard events, r=Gijs The virtual click event is also removed. It seems this event is only used to check whether this was a key or mouse event in PanelMultiView.jsm This also removes support for pressing the enter key to trigger these toolbarbuttons on Mac which shouldn't be happening anyway. Differential Revision: https://phabricator.services.mozilla.com/D149285

Bug 1682621, set input source to MOZ_SOURCE_KEYBOARD for command events on buttons, r=tnikkel Differential Revision: https://phabricator.services.mozilla.com/D149284

Merge autoland to mozilla-central. a=merge

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD dsb -> 7a4d435f8d7b2af6a8b058d10527511b990dc0e6 hsb -> ca0a7bd94556d1e228087ef61330794ede685126 kk -> 2e8445e6ef6c61c11cfd144c1e921a176478e4fe ru -> 26554d6f09489b38c3971db7c9cc3ba2b1fe1dd0 uk -> 7313454a1761f382ab7bffe2190288d7b73c1300

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD es-AR -> d7e544ebc5d098979c4ba8313b10e6a10d1d2af3 tg -> f6236bc1cbcb80c957a2f7f2f8a57b8057ff084b

Bug 1777768 - Update PDF.js to 13c01b6d4ababf039fe59ef800ebae38b1de37f5 r=pdfjs-reviewers,calixte Differential Revision: https://phabricator.services.mozilla.com/D150882

Bug 1737722. r=botond Differential Revision: https://phabricator.services.mozilla.com/D145721

Bug 1777657 - Remove SurfaceDescriptor from WebRenderTextureHost constructor r=gfx-reviewers,lsalzman SurfaceDescriptor is not used anymore in WebRenderTextureHost constructor. Differential Revision: https://phabricator.services.mozilla.com/D150853

Merge mozilla-central to autoland on a CLOSED TREE

Merge autoland to mozilla-central. a=merge

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD gn -> f2cdf894fe9d44468d9020bf87c538cbc1eaa9ce it -> 6fccaee01516e4485b5aa9ce58d8cc2a051949d9 pl -> 795c93e5a9d626917915831dcef027a07746d359 sl -> cd0bb38c209d76e711cdda4515f1182744adb8a4 tg -> b33a76f5393c5b6aa90a3fade759ed0355875661

Bug 1777466 - Added image display for selected colorway to FX View r=dao Added image display for selected colorway to FX View Differential Revision: https://phabricator.services.mozilla.com/D150748

Bug 1776202 - Pocket newtab recent saves adding my list link to top right of section r=gvn Differential Revision: https://phabricator.services.mozilla.com/D150500

Bug 1777338 - Make sure zoom command updater takes a user-set default zoom level into account. r=NeilDeakin The patch for bug 698873 assumed that the default zoom level is 1.0, when the user can actually change that value. Interestingly, we have to asynchronously query for the default value, so for simplicities sake, I've had to update the test I wrote to poll for the commands to be in the right state. Differential Revision: https://phabricator.services.mozilla.com/D150700

Bug 1640762 - Reduce max-run-time for some tasks from 36000 to 10800. r=taskgraph-reviewers,jmaher DONTBUILD The longest of these tasks take around 1 hour and a half, by having a max runtime of 10 hours we risk wasting a lot of time in case of bugs. Differential Revision: https://phabricator.services.mozilla.com/D150855

Bug 1775043 - Hide subtitles setting panel when clicking on PiP window. r=pip-reviewers,mhowell This only fixes the issue on macOS and Linux. Differential Revision: https://phabricator.services.mozilla.com/D150802

Backed out changeset 566b061ee95d (bug 1777209) for causing multiple failures CLOSED TREE

Bug 1777531 - Persist the selected intensity when toggling between colorway radios. r=bigiri Differential Revision: https://phabricator.services.mozilla.com/D150854

Bug 1777549 - remove remaining e10s conditions in manifest files. r=gbrown,extension-reviewers,zombie Differential Revision: https://phabricator.services.mozilla.com/D150820

Bug 1774183 - Improve test coverage of colorwaycloset.js r=Gijs Added tests to improve test coverage of colorwaycloset.js Differential Revision: https://phabricator.services.mozilla.com/D150158

Merge mozilla-central to autoland. CLOSED TREE

Merge autoland to mozilla-central. a=merge

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD dsb -> c19486d98cd655aacaee6126bb3057fc34b80a18 et -> 67aeab28137f4ad17cbbb4afa1ad1e4d5172562c hsb -> c6918f2ae2de0f5ad2d9a8c41671260f901f7665

Bug 1777209 - Use DrawSurface rather than FillRect to paint <canvas>, and don't use EXTEND_PAD when writing to PDF. r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D150601

Bug 1777186 [Wayland] Use correct popup window to calculate parent fit r=jhorak Differential Revision: https://phabricator.services.mozilla.com/D150537

Bug 1777564 - Enable the 'power' profiling feature when profiling from about:processes, r=gerald. Differential Revision: https://phabricator.services.mozilla.com/D150799

Backed out 1 changesets (bug 1773520) for breaking the ./mach ide vscode Backed out changeset d9571dde686f (bug 1773520)

Bug 1777482 - Disable helper_bug1756529 on Mac. r=hiro Differential Revision: https://phabricator.services.mozilla.com/D150851

Bug 1776332 - part 2: Create a tentative WPT to check attribute handling of joining elements by the builtin editor r=m_kato Similar to the previous patch, this adds tentative tests. Different from the previous tests, joining shouldn't touch attributes of the original nodes. This tests do not check which node is deleted from the document, but in the future, it should be tested after fixing bug 1735608 completely. Differential Revision: https://phabricator.services.mozilla.com/D150221

Bug 1776332 - part 1: Create a tentative WPT to check attribute handling of splitting element by the builtin editor r=m_kato We have similar tests under `mozilla`. However, for Interop2022-editing, we should rewrite it with the modern style and mark it "tentative". It does not matter how to split an element and its ancestors here. The test check only how attributes of splitting element and its ancestors. All attributes should be cloned, but `id` attributes shouldn't, at least, there should not be 2 elements which share same `id` value. Chrome duplicates `id` attributes, so Chrome fails to pass of the checks, but passes the other checks. Differential Revision: https://phabricator.services.mozilla.com/D150220

Bug 1776331 - Add check whether `document.execCommand("selectAll")` worked first r=m_kato Oddly, the test is passed in Chrome if only it runs, i.e., if I run all tests in the same folder, the test fails even in Chrome (currently, all browsers fail the test, Gecko's bug is bug 1771701, but the failure reason is different from the others). The original purpose of the test is, check where is selected by a `document.execCommand("selectAll")` call when no editable element has focus. Therefore, we want Chrome to pass it even with any hacks. However, adding some hacks makes it passes in Gecko too. Therefore, this patch just adds a new check which shows the failure reason correctly in Chrome. Differential Revision: https://phabricator.services.mozilla.com/D150219

Bug 1777652 - Minor followup fixes for bug 1530253. r=botond * Differential Revision: https://phabricator.services.mozilla.com/D150848

Bug 1768214 - introduce wasm32 codegen. r=jandem We are going to compile JS into WebAssembly! This is the first patch in an upcoming queue. Here we introduce wasm32 architecture so that SpiderMonkey can be compiled with enabled jit for wasi target. Differential Revision: https://phabricator.services.mozilla.com/D145790

Bug 1774114 - Make `HTMLEditor` and its helper classes get split/join node direction dynamically r=m_kato Currently I'm think that the split/join node direction should be managed per `HTMLEditor` instance because per transaction makes undo/redo handling complicated and may require additional space to save it in each transaction instance. However, the direction should be changeable with new Gecko specific `execCommand` to support both direction until creating first split/join node transaction or anytime with clearing the transactions. Differential Revision: https://phabricator.services.mozilla.com/D149192

Bug 1530253 - Trigger resnap on scroll-snap-type or scroll-snap-align changes. r=emilio Depends on D148863 Differential Revision: https://phabricator.services.mozilla.com/D148864

Bug 1530253 - Trigger re-snap on reflows and in RecomputePosition. r=botond,emilio The basic machinery to trigger re-snap is same as what scroll anchoring does, queueing a triggering request and flush the queued requests after reflows finished. Depends on D148862 Differential Revision: https://phabricator.services.mozilla.com/D148863

Bug 1530253 - Implement the logic to choose the best snap point for re-snap. r=botond Depends on D148861 Differential Revision: https://phabricator.services.mozilla.com/D148862

Bug 1530253 - Store the last snap target ids in the case of instant scroll oparations on the main-thread. r=botond,emilio Depends on D148860 Differential Revision: https://phabricator.services.mozilla.com/D148861

Bug 1530253 - Give the snap target ids to ScrollToWithOrigin. r=botond The snap targt ids will be the last snap target ids we use for re-snapping. Depends on D148859 Differential Revision: https://phabricator.services.mozilla.com/D148860

Bug 1530253 - Add a wrapper struct representing various arguments for ScrollToWithOrigin. r=botond Depends on D148858 Differential Revision: https://phabricator.services.mozilla.com/D148859

Bug 1530253 - Replace internal ScrollFrameHelper::ScrollTo calls with ScrollFrameHelper::ScrollToWithOrigin. r=botond There are some call sites of ScrollTo involving will a GetSnapPointForDestination call. For re-snapping, we need to inform not only the snap point but also the snap target id(s). To do it, in subsequent patches in this commit series, we will change only ScrollToWithOrigin arguments rather than both ScrollTo and ScrollToWithOrigin. Depends on D148857 Differential Revision: https://phabricator.services.mozilla.com/D148858

Bug 1530253 - Make GetSnapPointForDestination return the last snapped target id(s). r=botond Depends on D148856 Differential Revision: https://phabricator.services.mozilla.com/D148857

Bug 1530253 - Assign an id to each scroll snap target for tracking the last snapped element. r=botond,emilio Depends on D148855 Differential Revision: https://phabricator.services.mozilla.com/D148856

Bug 1530253 - Introduce a new struct wrapping various varibles in CalcSnapPoints. r=botond Differential Revision: https://phabricator.services.mozilla.com/D148855

Bug 1777586 - Bump cargo-vet. r=nika Differential Revision: https://phabricator.services.mozilla.com/D150843

Bug 1777586 - Audit some crates for kicks. r=nika,supply-chain-reviewers Differential Revision: https://phabricator.services.mozilla.com/D150842

Bug 1777586 - Regenerate exemptions. r=nika,supply-chain-reviewers This is needed after we set audit-as-crates-io = false for these crates. Differential Revision: https://phabricator.services.mozilla.com/D150841