07cc428541a410605ebf4d2b839a7e45672a4db4: Bug 1746527 - Make `browser/components/shell/test/browser_setDefaultPDFHandler.js` Windows 10+. r=bhearsum
Nick Alexander <nalexander@mozilla.com> - Sun, 27 Mar 2022 04:01:59 +0000 - rev 687338
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1746527 - Make `browser/components/shell/test/browser_setDefaultPDFHandler.js` Windows 10+. r=bhearsum Differential Revision: https://phabricator.services.mozilla.com/D142147
6318b1d2b7c859e15777cdaf7f3658cbf71a1ec2: Bug 1761216 - Update metadata for autoland failures, a=testonly
James Graham <james@hoppipolla.co.uk> - Sat, 26 Mar 2022 18:23:45 +0000 - rev 687337
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1761216 - Update metadata for autoland failures, a=testonly
ac304709067a402f969646f546f81b60f1d31ac8: Bug 1761216 - Update metadata for autoland failures, a=testonly
James Graham <james@hoppipolla.co.uk> - Sat, 26 Mar 2022 13:48:24 +0000 - rev 687336
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1761216 - Update metadata for autoland failures, a=testonly Differential Revision: https://phabricator.services.mozilla.com/D142155
1db538ddb4d37d4f15ad8e60a855e91402a35ab7: Bug 1761216 - [wpt-sync] Update web-platform-tests to 145e30f4a0f045c4d38da61d04727f509391e6e8, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 24 Mar 2022 12:41:01 +0000 - rev 687335
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1761216 - [wpt-sync] Update web-platform-tests to 145e30f4a0f045c4d38da61d04727f509391e6e8, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 145e30f4a0f045c4d38da61d04727f509391e6e8 wpt-type: landing
71353e2936d97e20f6eb8f2ced05d95a367683df: Bug 1760902 [wpt PR 33311] - Bump fonttools from 3.13.1 to 4.31.2 in /tools, a=testonly
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> - Thu, 24 Mar 2022 12:22:12 +0000 - rev 687334
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760902 [wpt PR 33311] - Bump fonttools from 3.13.1 to 4.31.2 in /tools, a=testonly Automatic update from web-platform-tests Bump fonttools from 3.13.1 to 4.31.2 in /tools Bumps [fonttools](https://github.com/fonttools/fonttools) from 3.13.1 to 4.31.2. - [Release notes](https://github.com/fonttools/fonttools/releases) - [Changelog](https://github.com/fonttools/fonttools/blob/main/NEWS.rst) - [Commits](https://github.com/fonttools/fonttools/compare/3.13.1...4.31.2) --- updated-dependencies: - dependency-name: fonttools dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> -- wpt-commits: 145e30f4a0f045c4d38da61d04727f509391e6e8 wpt-pr: 33311
c56c49c43d1102ea15e17e288c48ea247cb971fa: Bug 1760951 [wpt PR 33317] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 23 Mar 2022 10:57:00 +0000 - rev 687333
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760951 [wpt PR 33317] - Update wpt metadata, a=testonly wpt-pr: 33317 wpt-type: metadata
203717c0cfe2339cee58e4bb0d58018d1493ae93: Bug 1760951 [wpt PR 33317] - Iframes with missing redirect location should fire load event and queue RT entry, a=testonly
Noam Rosenthal <noamr@users.noreply.github.com> - Thu, 24 Mar 2022 12:22:03 +0000 - rev 687332
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760951 [wpt PR 33317] - Iframes with missing redirect location should fire load event and queue RT entry, a=testonly Automatic update from web-platform-tests Iframes with missing redirect location should fire load event and queue RT entry (#33317) * Iframes with missing redirect location should fire load event and queue RT entry See https://github.com/whatwg/html/pull/7531 * Rename and use loader -- wpt-commits: 7eb2cb2120e6cd172ad10edb7f38518e765daf49 wpt-pr: 33317
12b1423d447f562d686fd42a7a8595e1392b17e3: Bug 1760642 [wpt PR 33286] - Unify wpt test drawing-images-to-the-canvas, a=testonly
Yi Xu <yiyix@chromium.org> - Thu, 24 Mar 2022 12:21:55 +0000 - rev 687331
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760642 [wpt PR 33286] - Unify wpt test drawing-images-to-the-canvas, a=testonly Automatic update from web-platform-tests Unify wpt test drawing-images-to-the-canvas Unify wpt test drawing-images-to-the-canvas for both HTMLCanvas and OffscreenCanvas. Bug: 1275750 Change-Id: I5eee4f187ad09214222e985d3b001168fdcc8871 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3536424 Reviewed-by: Juanmi Huertas <juanmihd@chromium.org> Commit-Queue: Yi Xu <yiyix@chromium.org> Cr-Commit-Position: refs/heads/main@{#984188} -- wpt-commits: f917fa0fbbbdb64ea38382e2f69d5168ac4fc40c wpt-pr: 33286
35ee4a724a64ce6850d17881df64b8afd2c1281f: Bug 1760923 [wpt PR 33315] - Remove an abstraction layer for Web Bundles WPT tests, a=testonly
Hayato Ito <hayato@chromium.org> - Thu, 24 Mar 2022 12:21:32 +0000 - rev 687330
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760923 [wpt PR 33315] - Remove an abstraction layer for Web Bundles WPT tests, a=testonly Automatic update from web-platform-tests Remove an abstraction layer for Web Bundles WPT tests A follow-up CL for https://crrev.com/c/3539725. Remove the most of wpt/web-bundle/subresource-loading/resources files, which were previously used from both <link>-based API and <script>-based API tests. They are now directly embedded in <script>-based API tests. This CL also removes window.TEST_WEB_BUNDLE_ELEMENT_TYPE hack from test-helper.js, which is no longer necessary. Bug: 1306725 Change-Id: Id47fd8691a87207a2fa4303285fa388d885f2d43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3541723 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/main@{#984168} -- wpt-commits: dfe10ec3f853fc68707c3e516a0a3e38639a32f4 wpt-pr: 33315
1959ed92ac1cf9268402a9c275b262ab236dc379: Bug 1760359 [wpt PR 33277] - [Gecko Bug 1760359] Don't use Thread.native_id since it requires Python 3.8, a=testonly, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 24 Mar 2022 12:20:37 +0000 - rev 687329
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760359 [wpt PR 33277] - [Gecko Bug 1760359] Don't use Thread.native_id since it requires Python 3.8, a=testonly, a=testonly Automatic update from web-platform-tests Don't use Thread.native_id since it requires Python 3.8, a=testonly bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1760359 gecko-commit: 45432042d98a285c2fec5395861eeaef9ad9c96a gecko-reviewers: testonly -- Remove unused import -- wpt-commits: d668cb86c30cff3d835ef7248c194eca444d9271, a96d5117f69ff37a200e9ae38edf668a5df55b79 wpt-pr: 33277
0c1ec5e698758b3c77849eedfb9b3486ec151bfa: Bug 1760909 [wpt PR 33312] - Properly remove / re-add moved children from / to the flow thread., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 24 Mar 2022 12:20:27 +0000 - rev 687328
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760909 [wpt PR 33312] - Properly remove / re-add moved children from / to the flow thread., a=testonly Automatic update from web-platform-tests Properly remove / re-add moved children from / to the flow thread. CL:3479936 added code to notify the flow thread about descendant removal "in time", but we forgot to notify the flow thread about the descendants (that we're going to keep) being "re-added". Request a full remove/insert, which will automatically call FlowThreadDescendantWillBeRemoved() and FlowThreadDescendantWasInserted() (in LayoutMultiColumnFlowThread) at the right times. Bug: 1308253, 1305865, 1308232 Change-Id: I39e0404bdc53136fa646d4664681facf0a6e35e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3541961 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#984108} -- wpt-commits: 37fc51acdbefdcf814e1de8645190a70089da22c wpt-pr: 33312
87bad8070d68fac2dcd63a99777fdd1f1b8827b7: Bug 1760895 [wpt PR 33310] - Reland "Create property tree nodes for will-change only when relevant property has will-change.", a=testonly
L. David Baron <dbaron@chromium.org> - Thu, 24 Mar 2022 12:20:20 +0000 - rev 687327
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760895 [wpt PR 33310] - Reland "Create property tree nodes for will-change only when relevant property has will-change.", a=testonly Automatic update from web-platform-tests Reland "Create property tree nodes for will-change only when relevant property has will-change." This is a reland of commit 5d3dd81ee4f41ffc7fd40fda745cb097cd50e9f5 Original change's description: > Create property tree nodes for will-change only when relevant property has will-change. > > Prior to this change, will-change: transform, opacity, filter, or > backdrop-filter would cause the creation of property tree nodes (in both > the paint property tree and the cc property tree) for all of them > (though only a single effect property node for both opacity and > backdrop-filter). > > With this change, will-change: transform only causes the creation of a > transform node (in the transform tree), will-change: filter only causes > the creation of a filter node (in the effect tree), and will-change: > opacity or backdrop-filter only causes the creation of an effect node > (in the effect tree). However, *if* the nodes are created by something > else, the presence of a different will-change still causes any node that > is created in the paint property tree to be composited (i.e., created in > the cc property tree). > > This provides the basis on which we can separate the transform node into > multiple transform nodes, for efficient implementation and animation of > individual transform properties, without causing a performance > regression. > > Earlier versions of this CL (prior to the change that kept nodes being > composited for an unrelated will-change) caused the test > external/wpt/css/filter-effects/effect-reference-feimage-002.html to > start failing (in the same way as -001 and -003) because the filter > effect is no longer composited. It creates a copy of the test as -004 > with will-change: filter rather than will-change: transform that > continues to have a composited filter effect node and thus continues > passing even with that earlier change. This test still seems worth > adding despite no longer strictly being needed. > > Bug: 900241 > Change-Id: I18efc630668ea7eac2a8c0a0417b766762e71d9f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3328730 > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Commit-Queue: David Baron <dbaron@chromium.org> > Cr-Commit-Position: refs/heads/main@{#983821} Bug: 900241 Change-Id: Ic760f2d303f56c1ab9c276a510b9eff82e53179b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3543395 Auto-Submit: David Baron <dbaron@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: David Baron <dbaron@chromium.org> Cr-Commit-Position: refs/heads/main@{#984106} -- wpt-commits: ed4f727e4e7960a8af929a51712c46b007ecadf1 wpt-pr: 33310
6015893a838a396e23a015e928a26b7eee2340c4: Bug 1760741 [wpt PR 33296] - Add WPT for Early Hints with arbitrary header, a=testonly
Kenichi Ishibashi <bashi@chromium.org> - Thu, 24 Mar 2022 12:20:13 +0000 - rev 687326
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760741 [wpt PR 33296] - Add WPT for Early Hints with arbitrary header, a=testonly Automatic update from web-platform-tests Add WPT for Early Hints with arbitrary header It should have no effect. Bug: 1305896 Change-Id: I088f0aa4dd8f992140c3a62fabff2bd1d4dd1f95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3539727 Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/main@{#984026} -- wpt-commits: aa4c1758f854c7c7954d2a3240d55bdaa24361d7 wpt-pr: 33296
eff90f125d0b23220ca67bd7cf9ceeb825d13d9e: Bug 1760777 [wpt PR 33298] - Add WPTs for COEP mismatch between Early Hints and the final response, a=testonly
Kenichi Ishibashi <bashi@chromium.org> - Thu, 24 Mar 2022 12:20:05 +0000 - rev 687325
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760777 [wpt PR 33298] - Add WPTs for COEP mismatch between Early Hints and the final response, a=testonly Automatic update from web-platform-tests Add WPTs for COEP mismatch between Early Hints and the final response The test scenario is that: * The test page sends an Early Hint response which contains a COEP header and a preload link header for a resource. The response doesn't specify Cross-Origin-Resource-Policy. * The test page sends the final response which contains an inconsistent COEP header with the Early Hints response. Bug: 1305896 Change-Id: I7c9f0812682524771a0264ac767ee63c9e0efda0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3539729 Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/main@{#984025} -- wpt-commits: 61c035d145bd12e310f6af593702f7e152679954 wpt-pr: 33298
6a00fe73b230ddb9377088c95585d7796a5d8371: Bug 1760890 [wpt PR 33308] - Revert "Create property tree nodes for will-change only when relevant property has will-change.", a=testonly
David Baron <dbaron@chromium.org> - Thu, 24 Mar 2022 12:19:50 +0000 - rev 687324
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760890 [wpt PR 33308] - Revert "Create property tree nodes for will-change only when relevant property has will-change.", a=testonly Automatic update from web-platform-tests Revert "Create property tree nodes for will-change only when relevant property has will-change." This reverts commit 5d3dd81ee4f41ffc7fd40fda745cb097cd50e9f5. Reason for revert: failure of fast/sub-pixel/transformed-iframe-copy-on-scroll.html on mac-mac11-arm64. Original change's description: > Create property tree nodes for will-change only when relevant property has will-change. > > Prior to this change, will-change: transform, opacity, filter, or > backdrop-filter would cause the creation of property tree nodes (in both > the paint property tree and the cc property tree) for all of them > (though only a single effect property node for both opacity and > backdrop-filter). > > With this change, will-change: transform only causes the creation of a > transform node (in the transform tree), will-change: filter only causes > the creation of a filter node (in the effect tree), and will-change: > opacity or backdrop-filter only causes the creation of an effect node > (in the effect tree). However, *if* the nodes are created by something > else, the presence of a different will-change still causes any node that > is created in the paint property tree to be composited (i.e., created in > the cc property tree). > > This provides the basis on which we can separate the transform node into > multiple transform nodes, for efficient implementation and animation of > individual transform properties, without causing a performance > regression. > > Earlier versions of this CL (prior to the change that kept nodes being > composited for an unrelated will-change) caused the test > external/wpt/css/filter-effects/effect-reference-feimage-002.html to > start failing (in the same way as -001 and -003) because the filter > effect is no longer composited. It creates a copy of the test as -004 > with will-change: filter rather than will-change: transform that > continues to have a composited filter effect node and thus continues > passing even with that earlier change. This test still seems worth > adding despite no longer strictly being needed. > > Bug: 900241 > Change-Id: I18efc630668ea7eac2a8c0a0417b766762e71d9f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3328730 > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Commit-Queue: David Baron <dbaron@chromium.org> > Cr-Commit-Position: refs/heads/main@{#983821} Bug: 900241 Change-Id: I8143ff91fa0d856ab189414e44f12ce1bcdf77e8 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3544106 Auto-Submit: David Baron <dbaron@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: David Baron <dbaron@chromium.org> Commit-Queue: David Baron <dbaron@chromium.org> Cr-Commit-Position: refs/heads/main@{#984017} -- wpt-commits: a96c12ebc2df6ca08a8c94f847d4b78d20ed6117 wpt-pr: 33308
b86efe1cdaef7838b8fb9b5ba32fb91c464554b0: Bug 1760544 [wpt PR 33276] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 21:52:47 +0000 - rev 687323
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760544 [wpt PR 33276] - Update wpt metadata, a=testonly wpt-pr: 33276 wpt-type: metadata
a8b49131eb625a7c1cc7600b21c12f05a4f7a6d2: Bug 1760544 [wpt PR 33276] - Ensure consistency of ButtonFace system color and button background., a=testonly
Jan Keitel <jkeitel@google.com> - Thu, 24 Mar 2022 12:19:27 +0000 - rev 687322
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760544 [wpt PR 33276] - Ensure consistency of ButtonFace system color and button background., a=testonly Automatic update from web-platform-tests Ensure consistency of ButtonFace system color and button background. According to CSS Color Module Level 4, ButtonFace is the background color on default-syle button elements. This CL resolves the current discrepancy, introduces additional tests and removes some ignored code. With this CL, all button-related colors should behave as they are supposed to. Bug: 1299441 Change-Id: I56ee1b993383c37aa920128f59556b97d8d6508e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3535440 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/main@{#984005} -- wpt-commits: 9dd86c4ac1a7262723bbb9ed56b194bb85a511a6 wpt-pr: 33276
6a629b39dba637e71941d67753aee4e367acb30c: Bug 1760868 [wpt PR 33305] - Update admins for wpt-live and wpt-pr-bot on GCP, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 24 Mar 2022 12:19:21 +0000 - rev 687321
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760868 [wpt PR 33305] - Update admins for wpt-live and wpt-pr-bot on GCP, a=testonly Automatic update from web-platform-tests Update admins for wpt-live and wpt-pr-bot on GCP (#33305) -- wpt-commits: 8939373237d42c33f51c3bd45b83c4a0fe9a05cc wpt-pr: 33305
7bc7abeb7bc1c3f03fe7ebadc5d822e96c51d515: Bug 1760682 [wpt PR 33287] - Navigation API: serialize state first in navigate()/reload(), a=testonly
Domenic Denicola <domenic@chromium.org> - Thu, 24 Mar 2022 12:19:15 +0000 - rev 687320
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760682 [wpt PR 33287] - Navigation API: serialize state first in navigate()/reload(), a=testonly Automatic update from web-platform-tests Navigation API: serialize state first in navigate()/reload() Follows https://github.com/WICG/navigation-api/pull/215. Bug: 1183545 Change-Id: Ia88d09993821dce59a7cbc2768941ff28db53277 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3540582 Reviewed-by: Nate Chapin <japhet@chromium.org> Commit-Queue: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/main@{#983988} -- wpt-commits: ada05ad83ef1ff9882abcacd3b3759be0253b4dd wpt-pr: 33287
27fb34fc4164a2aca1ae7fbfd54dc121312c3dd1: Bug 1760820 [wpt PR 33302] - Ensure correct depdencies for tools/wave and tools/wpt tests, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 24 Mar 2022 12:18:57 +0000 - rev 687319
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760820 [wpt PR 33302] - Ensure correct depdencies for tools/wave and tools/wpt tests, a=testonly Automatic update from web-platform-tests Ensure correct depdencies for tools/wave and tools/wpt tests The requirements.txt files were unused, and we must have been depending on depdencies being already installed. This was noticed when trying to support Python 3.10. mozinfo isn't used in tools/wpt/, so drop that dependency. -- wpt-commits: aaa06bbff3ad3e8c743287cd28862a433e187024 wpt-pr: 33302
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip