6385d5f5470bc0eb4e50c2ce3442883a3f7f0c52: Bug 1635712 [wpt PR 23414] - Move scroll-anchoring tests to WPT, a=testonly
Nick Burris <nburris@chromium.org> - Wed, 13 May 2020 09:43:14 +0000 - rev 530036
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635712 [wpt PR 23414] - Move scroll-anchoring tests to WPT, a=testonly Automatic update from web-platform-tests Move scroll-anchoring tests to WPT Change-Id: I97fe58e63eae178396249cc0ed6692f5c8f2e22d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182737 Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Commit-Queue: Nick Burris <nburris@chromium.org> Cr-Commit-Position: refs/heads/master@{#765996} -- wpt-commits: 59e50d35ef02a8992dce8980784c14010ebf7c98 wpt-pr: 23414
5de79055b0a3c6b612a79801d4772b172aca364a: Bug 1635304 [wpt PR 23392] - Remove erroneous named properties object test, a=testonly
Domenic Denicola <d@domenic.me> - Wed, 13 May 2020 09:43:09 +0000 - rev 530035
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635304 [wpt PR 23392] - Remove erroneous named properties object test, a=testonly Automatic update from web-platform-tests Remove erroneous named properties object test Fixes #23391. -- wpt-commits: d61c071417775c037d9125b8519e972ade047b42 wpt-pr: 23392
8a4401aa7e894535f1dfdec34b015b3bf1b60468: Bug 1634510 [wpt PR 23348] - [css-flexbox] remove ttwf-reftest- prefix on 10 tests, a=testonly
Philip Jägenstedt <philip@foolip.org> - Wed, 13 May 2020 09:43:04 +0000 - rev 530034
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634510 [wpt PR 23348] - [css-flexbox] remove ttwf-reftest- prefix on 10 tests, a=testonly Automatic update from web-platform-tests [css-flexbox] remove ttwf-reftest- prefix on 10 tests (#23348) -- wpt-commits: bdfac9db8f03f32733aaeb2bd512c595c56fe2ab wpt-pr: 23348
697737336cb34432bdb19baffd88150255808ea7: Bug 1635782 [wpt PR 23431] - Fix stash ID in //fetch/metadata/preload.https.sub.html, a=testonly
Mike West <mkwst@google.com> - Wed, 13 May 2020 09:42:57 +0000 - rev 530033
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635782 [wpt PR 23431] - Fix stash ID in //fetch/metadata/preload.https.sub.html, a=testonly Automatic update from web-platform-tests Fix stash ID in //fetch/metadata/preload.https.sub.html `"{{uuid()}}"` is locked in when the page is generated, meaning that the generated subtests were all using the same random string for their stash storage. Which was dumb and my fault. This patch generates new stash IDs at runtime via `token()`. h/t @jgraham in https://bugzilla.mozilla.org/show_bug.cgi?id=1635614. -- wpt-commits: 6097d27b0ca2c105b15243aef702a093025e49e2 wpt-pr: 23431
1e3eb5c49723a920c8c47c05c3ce11623e234b1c: Bug 1635817 [wpt PR 23424] - Revert "[FlexNG] Make ComputeMinMaxSizes cache more precise.", a=testonly
Balazs Engedy <engedy@chromium.org> - Wed, 13 May 2020 09:42:50 +0000 - rev 530032
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635817 [wpt PR 23424] - Revert "[FlexNG] Make ComputeMinMaxSizes cache more precise.", a=testonly Automatic update from web-platform-tests Revert "[FlexNG] Make ComputeMinMaxSizes cache more precise." This reverts commit 044aeb3ed3364905cc185d67eb947c7ca3c13741. Reason for revert: Use-of-uninitialized-value. https://test-results.appspot.com/data/layout_results/WebKit_Linux_MSAN/5663/blink_web_tests/layout-test-results/results.html Original change's description: > [FlexNG] Make ComputeMinMaxSizes cache more precise. > > Previously our cache was imprecise, we recalculate our min/max sizes > when we didn't strictly need to, as we didn't know if we'd have a > %-block-size replaced element beneath us. > > This patch changes ComputeMinMaxSizes to return a MinMaxSizesResult > (instead of just MinMaxSizes). This contains an additional bit of > information to indicate if this sub-tree depended on the %-block-size > given to it. > > For most things, this will return false. For legacy layout roots we > always assume that they have children which depend on the %-block-size > (and why we initialize: > intrinsic_logical_widths_depends_on_percentage_block_size_ to true). > > Along with this change, the cache changes in the following way: > - We store an addition bit of information on LayoutBox to store the bit > of information from ComputeMinMaxSizes. > - We calculate the %-block-size for our children up-front, this means > each of the algorithms don't have to do this. > - With these changes, the cache can now hit, when the %-block-size > given to us changes. > > \o/ > > Bug: 845235 > Change-Id: I93504721dbdd13bef58917b1fab2cabbcd1ce51e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165676 > Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> > Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> > Reviewed-by: Morten Stenshorne <mstensho@chromium.org> > Reviewed-by: Koji Ishii <kojii@chromium.org> > Cr-Commit-Position: refs/heads/master@{#765797} TBR=cbiesinger@chromium.org,dgrogan@chromium.org,kojii@chromium.org,ikilpatrick@chromium.org,mstensho@chromium.org Change-Id: I9e5312e4a919fedbdc2cfd08e50a5f8b188e7a25 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 845235 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2184130 Reviewed-by: Balazs Engedy <engedy@chromium.org> Commit-Queue: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#765919} -- wpt-commits: b575c96e10e551afd314ace039360d3577276da9 wpt-pr: 23424
0600b9c3391ace4b846f0ba21e805480ee1e3f7d: Bug 1635815 [wpt PR 17573] - HTML: <thead height> et al are a thing, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Wed, 13 May 2020 09:42:45 +0000 - rev 530031
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635815 [wpt PR 17573] - HTML: <thead height> et al are a thing, a=testonly Automatic update from web-platform-tests HTML: <thead height> et al are a thing For https://github.com/whatwg/html/issues/4718. -- wpt-commits: 07b698ef4ea02ebeb65c3214ed7141ad32678a8c wpt-pr: 17573
f021dcb832316293e7d2ea357a27bb8c46e2dc06: Bug 1635813 [wpt PR 23417] - CookieStore: Add domain validation wpt for cookieStore.delete, a=testonly
Ayu Ishii <ayui@chromium.org> - Wed, 13 May 2020 09:42:40 +0000 - rev 530030
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635813 [wpt PR 23417] - CookieStore: Add domain validation wpt for cookieStore.delete, a=testonly Automatic update from web-platform-tests CookieStore: Add domain validation wpt for cookieStore.delete This change adds tests for domain validation in wpt for cookieStore.delete. Addresses comment: https://chromium-review.googlesource.com/c/chromium/src/+/2149699/2#message-e82e06fcb5fdc9ffb82e425114b2fc2adbf7d36c Bug: 729800 Change-Id: I3c12a5f6e2f8504d1b4c327120ec17af9be060b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2183193 Commit-Queue: Ayu Ishii <ayui@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#765866} -- wpt-commits: cf6daed503ac85776bbfe2299c18f569d29e5c0f wpt-pr: 23417
2cfe4a548db943fdb4cabf100918f437680dc2d6: Bug 1633999 [wpt PR 23311] - [css-flexbox] Implement gap/gutters in legacy flexbox, a=testonly
David Grogan <dgrogan@chromium.org> - Wed, 13 May 2020 09:42:35 +0000 - rev 530029
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1633999 [wpt PR 23311] - [css-flexbox] Implement gap/gutters in legacy flexbox, a=testonly Automatic update from web-platform-tests [css-flexbox] Implement gap/gutters in legacy flexbox This is primarily to support flexboxes that are laid out in legacy even after FlexNG ships, like <button> for which I added a test. Also flexboxes in contenteditable or multi-column contexts. Bug: 762679 Change-Id: Iade7f9f19db1a30b490f9d7203b72dc2275fbb0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2172758 Commit-Queue: David Grogan <dgrogan@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#765831} -- wpt-commits: 8c8fcc0a006d93cffa48b1d4613b8a44c3e34e94 wpt-pr: 23311
9c5ed78fdae79cdb01953c3153e2b27de6d74223: Bug 1634622 [wpt PR 23358] - [FlexNG] Make ComputeMinMaxSizes cache more precise., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Wed, 13 May 2020 09:42:30 +0000 - rev 530028
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634622 [wpt PR 23358] - [FlexNG] Make ComputeMinMaxSizes cache more precise., a=testonly Automatic update from web-platform-tests [FlexNG] Make ComputeMinMaxSizes cache more precise. Previously our cache was imprecise, we recalculate our min/max sizes when we didn't strictly need to, as we didn't know if we'd have a %-block-size replaced element beneath us. This patch changes ComputeMinMaxSizes to return a MinMaxSizesResult (instead of just MinMaxSizes). This contains an additional bit of information to indicate if this sub-tree depended on the %-block-size given to it. For most things, this will return false. For legacy layout roots we always assume that they have children which depend on the %-block-size (and why we initialize: intrinsic_logical_widths_depends_on_percentage_block_size_ to true). Along with this change, the cache changes in the following way: - We store an addition bit of information on LayoutBox to store the bit of information from ComputeMinMaxSizes. - We calculate the %-block-size for our children up-front, this means each of the algorithms don't have to do this. - With these changes, the cache can now hit, when the %-block-size given to us changes. \o/ Bug: 845235 Change-Id: I93504721dbdd13bef58917b1fab2cabbcd1ce51e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165676 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#765797} -- wpt-commits: 76e181c868d50d7f9a3901af03249102451d5de7 wpt-pr: 23358
4c8c1aae1c9b59438128bd11a253d5e00cff259b: Bug 1635593 [wpt PR 23409] - Fix testharness.js's assert_object_equals error message, a=testonly
Oriol Brufau <obrufau@igalia.com> - Wed, 13 May 2020 09:42:25 +0000 - rev 530027
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635593 [wpt PR 23409] - Fix testharness.js's assert_object_equals error message, a=testonly Automatic update from web-platform-tests Fix testharness.js's assert_object_equals error message When using assert_object_equals, if the two objects have the same property but with different values, then the error message used to say that the actual and expected values of the property were the root objects themselves. This patch fixes it so that the error message references the actual and expected value of the property. Change-Id: If9e6a5445db13444e22fd58729614c8c73046aea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181322 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#765713} -- wpt-commits: 027bdebf6a3052d664903d4488170a16419837ef wpt-pr: 23409
0b8d699ede30a5c3960e7f8211573a3213543470: Bug 1634161 [wpt PR 23325] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 May 2020 18:44:11 +0000 - rev 530026
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634161 [wpt PR 23325] - Update wpt metadata, a=testonly wpt-pr: 23325 wpt-type: metadata
d90d43b8b0d2802540dfcf24d4b7edf5e580c913: Bug 1634161 [wpt PR 23325] - [AspectRatio] Implement aspect ratio support for blocks, a=testonly
Christian Biesinger <cbiesinger@chromium.org> - Wed, 13 May 2020 09:42:17 +0000 - rev 530025
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634161 [wpt PR 23325] - [AspectRatio] Implement aspect ratio support for blocks, a=testonly Automatic update from web-platform-tests [AspectRatio] Implement aspect ratio support for blocks Bug: 1045668 Change-Id: Ib784cc4d69e7b1e02490f88b2b5262f72adf15e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151827 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#765688} -- wpt-commits: 4ed544ba95fa011524d36e0b21e88994dac55319 wpt-pr: 23325
b183b4ccbbe0cc55fbfd32562d12c93db1eaa576: Bug 1634697 [wpt PR 23360] - [WIP] Add interfaces/periodic-background-sync.idl and update test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 13 May 2020 09:42:12 +0000 - rev 530024
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634697 [wpt PR 23360] - [WIP] Add interfaces/periodic-background-sync.idl and update test, a=testonly Automatic update from web-platform-tests Add interfaces/periodic-background-sync.idl and update test (#23360) Closes https://github.com/web-platform-tests/wpt/pull/23342 -- wpt-commits: 7c823f650aed3593facdaf66c13394ef4a8ce347 wpt-pr: 23360
f329a21efb6a2c76a0b8d52666a277327239c190: Bug 1635323 [wpt PR 23397] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 May 2020 18:40:40 +0000 - rev 530023
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635323 [wpt PR 23397] - Update wpt metadata, a=testonly wpt-pr: 23397 wpt-type: metadata
5ebe3065955ee357d5a84bf0ee12cecb16b390a2: Bug 1635323 [wpt PR 23397] - Roll webidl2.js to master, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 13 May 2020 09:41:55 +0000 - rev 530022
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635323 [wpt PR 23397] - Roll webidl2.js to master, a=testonly Automatic update from web-platform-tests Roll webidl2.js to master (#23397) This updates webidl2.js to https://github.com/w3c/webidl2.js/commit/6107689a9241d2b37e6741b58fa23074623ff23b Fixes https://github.com/web-platform-tests/wpt/issues/23328 -- wpt-commits: f9709adf63adb8c316209e7826f67f3f9c2bf2f2 wpt-pr: 23397
2c48ea79c3184c6554f38b831ca6ca1ac44188c6: Bug 1633074 [wpt PR 23246] - Add some badges to README, a=testonly
Robert Ma <robertma@chromium.org> - Wed, 13 May 2020 09:41:48 +0000 - rev 530021
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1633074 [wpt PR 23246] - Add some badges to README, a=testonly Automatic update from web-platform-tests Add some badges to README * GitHub Actions (for the manifest & documentation workflows) * Python 3 blocker counter from pyup.io -- Add links -- wpt-commits: 49ae5abfba7ae9fa4520958b0dc2c508514ef0c8, 9f85748a60c4c1fb1fd910a3ea21708418e01584 wpt-pr: 23246
5b9c257df30d1f30a04d744a20d574b469ce2381: Bug 1634183 [wpt PR 23327] - [wptserve] Make cookies always binary strings, a=testonly
Robert Ma <robertma@chromium.org> - Wed, 13 May 2020 09:41:43 +0000 - rev 530020
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634183 [wpt PR 23327] - [wptserve] Make cookies always binary strings, a=testonly Automatic update from web-platform-tests [wptserve] Make cookies always binary strings (#23327) Change cookies on both Request and Response to always accept and return binary strings. Affected APIs: * Request.cookies * Response.{set,unset,delete}_cookie (Note that only name and value are converted at the moment.) Fix unit tests and infrastructure/ tests in Python 3. -- wpt-commits: e030609933ab7f98b1f757e41e80e96f5457e404 wpt-pr: 23327
42255f44a64a65eebb4c6d0922566674b53264de: Bug 1634613 [wpt PR 23357] - Make canvas test generation python3 compatible, a=testonly
Aaron Krajeski <krajeski@gmail.com> - Wed, 13 May 2020 09:41:37 +0000 - rev 530019
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634613 [wpt PR 23357] - Make canvas test generation python3 compatible, a=testonly Automatic update from web-platform-tests Make canvas test generation python3 compatible (#23357) * Make test generation python3 compatible * Get rid of test line * Fix range -- wpt-commits: 174ebae65f57434e771b44e4e2bd00df3000c79a wpt-pr: 23357
04a37833dbd2a81c39038b166f190514f95e692f: Bug 1635337 [wpt PR 23399] - Support Function in IdlArray.prototype.assert_type_is, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 13 May 2020 09:41:27 +0000 - rev 530018
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635337 [wpt PR 23399] - Support Function in IdlArray.prototype.assert_type_is, a=testonly Automatic update from web-platform-tests Support Function in IdlArray.prototype.assert_type_is (#23399) Closes https://github.com/web-platform-tests/wpt/issues/23329 -- wpt-commits: 550e0b3aee12752968f5a1204a6cf37f2bd5d83b wpt-pr: 23399
4399371f8772da4701844b409e1a3b23545d5d80: Bug 1629089 [wpt PR 22857] - Handle k-rate AudioParam inputs for BiquadFilterNode, a=testonly
Raymond Toy <rtoy@chromium.org> - Wed, 13 May 2020 09:41:22 +0000 - rev 530017
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1629089 [wpt PR 22857] - Handle k-rate AudioParam inputs for BiquadFilterNode, a=testonly Automatic update from web-platform-tests Handle k-rate AudioParam inputs for BiquadFilterNode Support k-rate input to AudioParams for a BiquadFilterNode. Previously, inputs to a k-rate AudioParam was ignored, which is incorrect. The input must be summed with any timeline value. Manually ran the new test case with Chrome stable and all the tests fail as expected. Bug: 1015760 Test: k-rate-biquad-connections.html Change-Id: Iec7b57fe3b730d4f5984e223fde9cef9a4402103 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144687 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#765606} -- wpt-commits: 100d85cd2b2fb476699f9c56fd543191c7c0a321 wpt-pr: 22857
0c392fcc97ed43bbd5324691906a45bea89cafb8: Bug 1635342 [wpt PR 23400] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 06 May 2020 06:43:24 +0000 - rev 530016
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635342 [wpt PR 23400] - Update wpt metadata, a=testonly wpt-pr: 23400 wpt-type: metadata
267d7af3baff396cd778e274e6c41c9f59189be8: Bug 1635342 [wpt PR 23400] - [EventTiming] Add a test for auxclick, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Wed, 13 May 2020 09:41:13 +0000 - rev 530015
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635342 [wpt PR 23400] - [EventTiming] Add a test for auxclick, a=testonly Automatic update from web-platform-tests [EventTiming] Add a test for auxclick This CL adds a helper function to add a test for an event type. The test will add two fast events of the event type and one slow one and test that the eventCounts as well as the entry in the PerformanceObserver for the slow event. Bug: 543598 Change-Id: I37da66424e7ea353b99787c578b26e3322cd984e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181147 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#765537} -- wpt-commits: 471e15e649002cb334f8b89d8b4a9ebb5122e437 wpt-pr: 23400
fdaa51024719d3153fd075a2b3e18c6c5009e97c: Bug 1633606 [wpt PR 23284] - [wptserve] Make sure GET/POST params are always binary, a=testonly
Robert Ma <robertma@chromium.org> - Wed, 13 May 2020 09:41:08 +0000 - rev 530014
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1633606 [wpt PR 23284] - [wptserve] Make sure GET/POST params are always binary, a=testonly Automatic update from web-platform-tests [wptserve] Make sure GET/POST params are always binary (#23284) * [wptserve] Fix RequestHeaders.get in Python 3 When there are multiple headers with the same name, this method would crash in Python 3 when attempting to join them. Drive-by: * Clean up Request.__init__ to make the logic clearer and an unnecessary access to the headers property. * Add some FIXMEs for more potential Py3 issues. * Add some tests to make sure Request.url can be constructed correctly as it uses some native strings intentionally. * WIP * Fix file upload, stash, and substitution pipe in Python 3 * Apply suggestions from code review * isomorphic_{encode,decode} * Address some comments * Fix file_upload in Python 3 * Fix a typo * add comment -- wpt-commits: c207ae61bf2a46e4fcadd03ca76af44e866f4c79 wpt-pr: 23284
2b16450fca689e9c6f77a7ae1a14e3f0e9912560: Bug 1635306 [wpt PR 23393] - Add rAF delays before cross-origin clicks to fix flakiness., a=testonly
Mustaq Ahmed <mustaq@google.com> - Wed, 13 May 2020 09:41:03 +0000 - rev 530013
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635306 [wpt PR 23393] - Add rAF delays before cross-origin clicks to fix flakiness., a=testonly Automatic update from web-platform-tests Add rAF delays before cross-origin clicks to fix flakiness. For cross-origin frames in WPTs, just waiting for all frames to load is not enough because cross-origin frame's hit-test data may not be ready by that time for the click to work correctly. This caused flakiness in all three cross-origin tests for user-activation. This CL adds rAF delays (after frame load completion) so that the clicks can get through correctly. Other changes: switched all async tests into sync tests nested inside a single async test to make the code easier to follow. Bug: 1064422, 1066178, 1066190 Change-Id: I853ff032c8050203abc72d89f0d6276af5102beb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2174887 Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#765543} -- wpt-commits: 6eea984f808b5c47fc506bced9b40372652d0c0e wpt-pr: 23393
81572d467873741a07973db4a2b35f9777772503: Bug 1635541 [wpt PR 23408] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 May 2020 18:34:09 +0000 - rev 530012
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635541 [wpt PR 23408] - Update wpt metadata, a=testonly wpt-pr: 23408 wpt-type: metadata
c389789d23c2ae742586011c4df4001da05fd60a: Bug 1635541 [wpt PR 23408] - Update interfaces/html.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 13 May 2020 09:40:48 +0000 - rev 530011
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635541 [wpt PR 23408] - Update interfaces/html.idl, a=testonly Automatic update from web-platform-tests Update interfaces/html.idl (#23408) Source: https://github.com/tidoust/reffy-reports/blob/8903dbd/ed/idl/html.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/683358012 -- wpt-commits: 7fab1c9029e800b8c199cab393fcd6a7ea85ee61 wpt-pr: 23408
912dee6ba76e9b43d50fc77da6f6d93d5f5d61c3: Bug 1635217 [wpt PR 23388] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 06 May 2020 06:12:55 +0000 - rev 530010
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635217 [wpt PR 23388] - Update wpt metadata, a=testonly wpt-pr: 23388 wpt-type: metadata
f1c61d14947ab4916203c8ac6b3a5bc806d46820: Bug 1635217 [wpt PR 23388] - Add WPT tests for bug 1074317, a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Wed, 13 May 2020 09:40:40 +0000 - rev 530009
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635217 [wpt PR 23388] - Add WPT tests for bug 1074317, a=testonly Automatic update from web-platform-tests Add WPT tests for bug 1074317 BUG=1074317 Change-Id: I3bcc915642b06f1370fe15d2331014297992adfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2179508 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#765533} -- wpt-commits: 5841e8d23091853f553935e9d0eeba1cd812c1ec wpt-pr: 23388
8b49336c002139632a13f8bdc7a541dde475284e: Bug 1635479 [wpt PR 23407] - Treat -webkit-writing-mode as animation-affecting, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Wed, 13 May 2020 09:40:35 +0000 - rev 530008
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635479 [wpt PR 23407] - Treat -webkit-writing-mode as animation-affecting, a=testonly Automatic update from web-platform-tests Treat -webkit-writing-mode as animation-affecting Since writing-mode is an animation-affecting property, -webkit- writing-mode must be as well, since it's a surrogate of writing-mode. There's an underlying bug in the StyleCascade related to animation of surrogates. For surrogates that are kHighPropertyPriority, the bug causes a crash, because we're attempting to lookup a property that isn't being animated. For other properties, it causes the surrogate to silently not be applied. Since -webkit-writing-mode is the only high-priority surrogate that exists, making it disallowed in animations effectively makes the crash unreachable. I'll address the greater issue separately. Bug: 1077501 Change-Id: I5df40337b88a1621ecbe20be04149ca2d6e9dfb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181209 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#765523} -- wpt-commits: 7de10f60511ace754ac4a0d030416132278ceac3 wpt-pr: 23407
8ee704cc798a38b8f415e98059a143e85e19cc46: Bug 1635315 [wpt PR 23394] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 May 2020 19:03:14 +0000 - rev 530007
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635315 [wpt PR 23394] - Update wpt metadata, a=testonly wpt-pr: 23394 wpt-type: metadata
e6a223161a0192e54472b13625f4797d01fa4796: Bug 1635316 [wpt PR 23395] - [css-pseudo] Add test for 'revert' in ::marker, a=testonly
Oriol Brufau <obrufau@igalia.com> - Wed, 13 May 2020 09:40:25 +0000 - rev 530006
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635316 [wpt PR 23395] - [css-pseudo] Add test for 'revert' in ::marker, a=testonly Automatic update from web-platform-tests [css-pseudo] Add test for 'revert' in ::marker The UA styles for ::marker were implemented in a hacky way that needs to be improved, then the 'revert' keyword doesn't work in ::marker. This patch adds a test to track this problem. BUG=457718 Change-Id: I5aecdf550efb350a70709b9d743142ae9e0e430b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181202 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#765486} -- wpt-commits: 664d6c5556092f71949ebc50f77724ea35f28d27 wpt-pr: 23395
e765268e21119f7ff7c9d73697a49d8380345e4b: Bug 1635539 [wpt PR 23405] - List default globals in prototypes.any.js, a=testonly
Ms2ger <Ms2ger@gmail.com> - Wed, 13 May 2020 09:40:20 +0000 - rev 530005
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635539 [wpt PR 23405] - List default globals in prototypes.any.js, a=testonly Automatic update from web-platform-tests List default globals in prototypes.any.js -- wpt-commits: 8c480f0835bc8564c44a5a29c4c0282d0ae94839 wpt-pr: 23405
4cdd5e7c02c4139f4e3c62acbb48a1e0cfc1fb6d: Bug 1634297 [wpt PR 23336] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 30 Apr 2020 09:09:28 +0000 - rev 530004
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634297 [wpt PR 23336] - Update wpt metadata, a=testonly wpt-pr: 23336 wpt-type: metadata
7d6082e757cb075e426e0b922fe4a3be3fbcbb94: Bug 1634297 [wpt PR 23336] - [shadow-dom] rename slotable to slottable, a=testonly
Philip Jägenstedt <philip@foolip.org> - Wed, 13 May 2020 09:40:11 +0000 - rev 530003
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634297 [wpt PR 23336] - [shadow-dom] rename slotable to slottable, a=testonly Automatic update from web-platform-tests DOM: rename slotable to slottable Follows https://github.com/whatwg/dom/pull/845. -- wpt-commits: a35a7400d6e34863e34b0cd5d708ad68286878b8 wpt-pr: 23336
22978f4eca60bdcec1a08c5cea764391a5977c49: Bug 1634942 [wpt PR 23376] - [ua-ch] Add support for Sec-CH-UA-Platform-Version, a=testonly
Yoav Weiss <yoavweiss@chromium.org> - Wed, 13 May 2020 09:40:06 +0000 - rev 530002
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634942 [wpt PR 23376] - [ua-ch] Add support for Sec-CH-UA-Platform-Version, a=testonly Automatic update from web-platform-tests [ua-ch] Add support for Sec-CH-UA-Platform-Version The platform version was split out of the Sec-CH-UA-Platform header[1], but the Client Hint version of it wasn't implemented. This CL fixes that. [1] https://github.com/WICG/ua-client-hints/pull/64 Bug: 1076933 Change-Id: I6670673c160f88e5df22814b36b327711c2529a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2172308 Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Aaron Tagliaboschi <aarontag@chromium.org> Reviewed-by: Maksim Orlovich <morlovich@chromium.org> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#765459} -- wpt-commits: 31c87db730fd5ad74f9cda802ca572345557ff2c wpt-pr: 23376
ea32130c91cb0aea273fb60b236bde657c6f1a7b: Bug 1635418 [wpt PR 23403] - webrtc wpt: mark simulcast tests as long, a=testonly
Philipp Hancke <philipp.hancke@googlemail.com> - Wed, 13 May 2020 09:39:59 +0000 - rev 530001
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635418 [wpt PR 23403] - webrtc wpt: mark simulcast tests as long, a=testonly Automatic update from web-platform-tests webrtc wpt: mark simulcast tests as long Bug: chromium:1077194 Change-Id: I41176080b71e2f5a99c5fda88cf6e1708209675b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181284 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#765439} -- wpt-commits: cda6502c06b8955d3146cad98ac384e72c41e252 wpt-pr: 23403
7497cfcc89b88bcbc11c1325ba70865d15652eb4: Bug 1593063 [wpt PR 20030] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 May 2020 20:19:00 +0000 - rev 530000
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1593063 [wpt PR 20030] - Update wpt metadata, a=testonly wpt-pr: 20030 wpt-type: metadata
aa30e97ff8f468b51c981cc3a9a357219fe3a38a: Bug 1593063 [wpt PR 20030] - Added 7 new CSS4Pseudo tests and 3 references, a=testonly
Gérard Talbot <github@gtalbot.org> - Wed, 13 May 2020 09:39:50 +0000 - rev 529999
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1593063 [wpt PR 20030] - Added 7 new CSS4Pseudo tests and 3 references, a=testonly Automatic update from web-platform-tests Added 7 new CSS4Pseudo tests and 3 references -- Improved highlight-z-index-* tests -- Corrected highlight-z-index-00[1-2].html tests -- Corrected highlight-z-index-00[1-2].html tests -- wpt-commits: 4b953890fe7217bdbd20d2777bc32687ef2a2d92, 41d824c80080b7e3eba3fdf522512bd4efeaa932, 472d91adc81ec070295abc98b3e59282874a1c37, 3adb0f89d80bb92ea1a458b3fbe461f7803549a9 wpt-pr: 20030
273397b59609d3cce84785704d6320db0df91b41: Bug 1625005 [wpt PR 22452] - Make commitStyles use computed values instead of resolved values, a=testonly
George Steel <gtsteel@google.com> - Wed, 13 May 2020 09:39:45 +0000 - rev 529998
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1625005 [wpt PR 22452] - Make commitStyles use computed values instead of resolved values, a=testonly Automatic update from web-platform-tests Make commitStyles use computed values instead of resolved values Add new CSSAnimationUtils class with a static method KeyframeValueFromComputedStyle() which returns the true computed value for all properties. This mostly calls CSSValueForComputedStyle() without a LayoutObject, but the cases where this does not return the computed value (line-height and transform) are handles separately, similarly to the implementation of ComputedStyleMap. This method does take a LayoutObject, but it is only used to resolve matrix interpolation of box-size-dependent transform values, which produces a deferred compilation which cannot be serialized directly in the current spec. Make Animation.commitStyles() use this new function instead of committing the resolved value using CSSValueFromComputedStyle(). Add additional WPT tests for commitStyles() adding tests for special-case properties and splitting the logical properties case. Bug: 1056197, 1057307 Change-Id: Ic823f96f257d4c6b010dfee758d4ac0b5cd4148c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2118765 Commit-Queue: George Steel <gtsteel@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Reviewed-by: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#765297} -- wpt-commits: c7c25c159ab2cc3d308c2cb033d31573c87854ef wpt-pr: 22452
9fb6c336ec1409f42f9c30a1adbaf81a0c57046c: Bug 1629179 [wpt PR 22860] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 May 2020 11:56:52 +0000 - rev 529997
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1629179 [wpt PR 22860] - Update wpt metadata, a=testonly wpt-pr: 22860 wpt-type: metadata
3bea7f4bce08afa08c241615753bfef8daa04ec2: Bug 1629179 [wpt PR 22860] - Handle k-rate AudioParam inputs for DynamicsCompressorNode, a=testonly
Raymond Toy <rtoy@chromium.org> - Wed, 13 May 2020 09:39:37 +0000 - rev 529996
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1629179 [wpt PR 22860] - Handle k-rate AudioParam inputs for DynamicsCompressorNode, a=testonly Automatic update from web-platform-tests Handle k-rate AudioParam inputs for DynamicsCompressorNode Support k-rate input to the AudioParms for a DynamicsCompressorNode. The node only has k-rate AudioParams so we just need to make sure the input is used. Manually ran this test on Chrome stable, and all tests fail as expected since k-rate inputs are not working there. Bug: 1015760 Test: k-rate-dynamics-compressor-connections.html Change-Id: I9ddaf27be5f2fef65f394f3d63f1fa8998c0ed82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2145814 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#765309} -- wpt-commits: a135e5f5e761e5650519c35fa8dac59f87d1074d wpt-pr: 22860
5fa2fa5c41009619d4c0e5e1affcc91ed300585c: Bug 1634118 [wpt PR 23321] - Add transition generation to CSS Transition, a=testonly
haozhe <haozhes@chromium.org> - Wed, 13 May 2020 09:39:32 +0000 - rev 529995
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634118 [wpt PR 23321] - Add transition generation to CSS Transition, a=testonly Automatic update from web-platform-tests Add transition generation to CSS Transition This patch added the transition generation which described in the spec: https://drafts.csswg.org/css-transitions-2/#current-transition-generation-section For two transitions with the same owning element (including the pseudo-element selector), this patch will sort animation1 and animation2 first by their transition generations, then in ascending order by the Unicode codepoints that make up the expanded transition property name of each transition The spec: https://drafts.csswg.org/css-transitions-2/#animation-composite-order Bug: 1072480, 1068740 Change-Id: I0f54f676befd250082b2323723ba2b71e2931b14 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157682 Commit-Queue: Hao Sheng <haozhes@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Reviewed-by: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#765305} -- wpt-commits: 3e0da6635e95c8c1161b9837c3d4acf9dbb42f30 wpt-pr: 23321
3c129f7713662d06dcf674152e52b2e3acd48f3b: Bug 1629063 [wpt PR 22856] - [css-variables] Clone style when there are no variable references, a=testonly
Javier Fernandez <jfernandez@igalia.com> - Wed, 13 May 2020 09:39:27 +0000 - rev 529994
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1629063 [wpt PR 22856] - [css-variables] Clone style when there are no variable references, a=testonly Automatic update from web-platform-tests [css-variables] Clone style when there are no variable references When resolving the CSS Custom Properties inheritance, we recalculate all the styles of nodes in the hierarchy. Following a similar approach to the one used for 'independent properties', we can just clone the node's parent style and propagate just the InheritedVariables data structure. We'll only recalc the styles if a node has any variable reference, defined as :var(--*), to a custom property. Bug: 1056209 Change-Id: I81081e11cd69f06e69a6030b97fabce3a50630b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111172 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#765278} -- wpt-commits: 2237420ac3aeffa6cdd1ceff6d8b1886fa9005dc wpt-pr: 22856
e3f5022d2e985bdc8821dd721432da3e3b2f3b5f: Bug 1634157 [wpt PR 23324] - Remove assert_precondition from testharness.js, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 13 May 2020 09:39:22 +0000 - rev 529993
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634157 [wpt PR 23324] - Remove assert_precondition from testharness.js, a=testonly Automatic update from web-platform-tests Remove assert_precondition from testharness.js (#23324) This is being removed in favour of assert_implements / assert_implements_optional. See the RFC: https://github.com/web-platform-tests/rfcs/blob/master/rfcs/assert_precondition_rename.md -- wpt-commits: 5681e96ff1cc7f2516c73f377639011aee94bc26 wpt-pr: 23324
6b4bbb6a182964ef8ff2ac771d837402bfdbda62: Bug 1635043 [wpt PR 23379] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 May 2020 10:08:58 +0000 - rev 529992
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635043 [wpt PR 23379] - Update wpt metadata, a=testonly wpt-pr: 23379 wpt-type: metadata
08f9c82b1cae4a7a98792d5def9c22d8259c73e3: Bug 1635043 [wpt PR 23379] - Recalculate raster scales whenever the desired raster scale changes, a=testonly
Daniel Libby <dlibby@microsoft.com> - Wed, 13 May 2020 09:39:13 +0000 - rev 529991
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1635043 [wpt PR 23379] - Recalculate raster scales whenever the desired raster scale changes, a=testonly Automatic update from web-platform-tests Recalculate raster scales whenever the desired raster scale changes Previous change for moving directly composited images from Blink to cc missed the cases where the bounds changed in such a way that didn't trip the code to recalculate raster scale. This means we were re-rastering with an out of date scale, which can cause visible artifacts around the edges of the images. This change removes the misguided attempt to track raster scale aspect ratio and instead uses the desired raster scale to determine when we need to recalculate. Additionally, the check for whether we should directly composite was taking place too early. The decision can be made only after the ideal source scale is taken into account. The check moves to RecalculateRasterScales, and we fall back to the normal recalculation if the image cannot be directly composited (i.e. doing so would result in rendering artifacts). Bug:1075911 Change-Id: Iff0802429aee235ac4a557b181df9ec60a964ed6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2171921 Commit-Queue: Daniel Libby <dlibby@microsoft.com> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#765234} -- wpt-commits: ca53e3af96eed21417fb47a73eff181617532337 wpt-pr: 23379
a1684145f954eaaa314f02db6d3a8dbacaa70a74: Bug 1634725 [wpt PR 23361] - Convert a CLS end to end test to wrap a WPT., a=testonly
Steve Kobes <skobes@chromium.org> - Wed, 13 May 2020 09:39:08 +0000 - rev 529990
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1634725 [wpt PR 23361] - Convert a CLS end to end test to wrap a WPT., a=testonly Automatic update from web-platform-tests Convert a CLS end to end test to wrap a WPT. This unifies MetricIntegrationTest.LayoutInstability with the nearly identical simple-block-movement.html, and introduces an abstraction for communicating expectations from the WPT to the wrapper, so that they can be verified in a generic way against the trace data and UMA/UKM results. We'll use this technique for CLSAttribution_* in a follow-up. Bug: 1045064 Change-Id: I401af5cd0186ad3de930130694ff2fcf7b43ed7e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2175636 Reviewed-by: Robert Ma <robertma@chromium.org> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Commit-Queue: Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#765156} -- wpt-commits: 79ecaf1d76018b995c2d438c28873288abfafd12 wpt-pr: 23361
1e7a63b8201d7411a63ee35d8d27d433970ce1ef: Bug 1633854 [wpt PR 23304] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 May 2020 03:36:25 +0000 - rev 529989
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1633854 [wpt PR 23304] - Update wpt metadata, a=testonly wpt-pr: 23304 wpt-type: metadata
96e901867dfcb2aa4bf2fc301526ea4441709000: Bug 1633854 [wpt PR 23304] - Adds slotchange event when inserting and removing slotable for manual slot assignment., a=testonly
Yu Han <yuzhehan@chromium.org> - Wed, 13 May 2020 09:38:52 +0000 - rev 529988
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1633854 [wpt PR 23304] - Adds slotchange event when inserting and removing slotable for manual slot assignment., a=testonly Automatic update from web-platform-tests Adds slotchange event when inserting and removing slotable for manual slot assignment. This CL adds tests to ensure slotchange event is fired when assigned nodes or slots are removed. They also test that slotchange event isn't raised when slots and slotables are inserted within a shadow host w/ manual slot assignment shadow root. In addition to tests, this CL adds the ability to raised slotchange event when a slot containing assigned nodes is removed from the shadow root. Most of the other test cases have already been implemented because node insertion and removal run assign slottables algorithm. Bug: 869308 Change-Id: I80212af34e569f9b80261c24253f38fe91d05a68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2169577 Commit-Queue: Yu Han <yuzhehan@chromium.org> Reviewed-by: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#765096} -- wpt-commits: 1114960c812943c3c92b1a52735ed574b0f19558 wpt-pr: 23304
7e4ddbfd531abd83a7896eedbfc99b44101aae27: Bug 1633593 [wpt PR 23281] - [wptserve] Fix RequestHeaders.get in Python 3, a=testonly
Robert Ma <robertma@chromium.org> - Wed, 13 May 2020 09:38:47 +0000 - rev 529987
Push 37419 by archaeopteryx@coole-files.de at Fri, 15 May 2020 09:33:04 +0000
Bug 1633593 [wpt PR 23281] - [wptserve] Fix RequestHeaders.get in Python 3, a=testonly Automatic update from web-platform-tests [wptserve] Fix RequestHeaders.get in Python 3 (#23281) When there are multiple headers with the same name, this method would crash in Python 3 when attempting to join them. Drive-by: * Clean up Request.__init__ to make the logic clearer and an unnecessary access to the headers property. * Add some FIXMEs for more potential Py3 issues. * Add some tests to make sure Request.url can be constructed correctly as it uses some native strings intentionally. -- wpt-commits: c6704bb144ce7bb067315711ec1059e856e1edac wpt-pr: 23281
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 +50 +100 +300 +1000 +3000 tip