98d776c343841b81c3b947ea17354828c73ac175: Bug 1631513 [wpt PR 23121] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 20 Apr 2020 17:17:04 +0000 - rev 590716
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1631513 [wpt PR 23121] - Update wpt metadata, a=testonly wpt-pr: 23121 wpt-type: metadata
6f1046cc9a5639a5139819bf087e545aaefa017d: Bug 1631513 [wpt PR 23121] - Meta: remove need for !worker in workers/ tests, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 28 Apr 2020 11:39:16 +0000 - rev 590715
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1631513 [wpt PR 23121] - Meta: remove need for !worker in workers/ tests, a=testonly Automatic update from web-platform-tests Meta: remove need for !worker in workers/ tests Helps with #23111. -- wpt-commits: b7f09dc81131e15c19fec3a9e198257f9bc9b43e wpt-pr: 23121
f7498902204d3048f1f71fc9d8648f90cbf72734: Bug 1632310 [wpt PR 23186] - Add test for computed versus resolved style., a=testonly
Kevin Ellis <kevers@chromium.org> - Tue, 28 Apr 2020 11:39:11 +0000 - rev 590714
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632310 [wpt PR 23186] - Add test for computed versus resolved style., a=testonly Automatic update from web-platform-tests Add test for computed versus resolved style. Change-Id: I3b05d556f011ecca39b4573516c4c39d2ec1b415 Bug: 1057307 Change-Id: I3b05d556f011ecca39b4573516c4c39d2ec1b415 -- wpt-commits: db694b482439296306f64f26db16c58d46e4695a wpt-pr: 23186
b4c21d6c137e0e39e8b8a9364434136980cf957b: Bug 1631648 [wpt PR 23126] - WebXR - AR - adjust XRRay to match the spec, a=testonly
Piotr Bialecki <bialpio@chromium.org> - Tue, 28 Apr 2020 11:39:06 +0000 - rev 590713
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1631648 [wpt PR 23126] - WebXR - AR - adjust XRRay to match the spec, a=testonly Automatic update from web-platform-tests WebXR - AR - adjust XRRay to match the spec Bring XRRay up to spec, adjusting the behavior with changes introduced by PR: https://github.com/immersive-web/hit-test/pull/85 Additionally, fix Chrome's Web IDL to not rely on overloads. Change-Id: I98af1a4ed90dbeb8e311795e818efb64bb15034d -- wpt-commits: fd045759df43fa155b34a5e4fe4187610ad1bb24 wpt-pr: 23126
74704c4f3d2dabe554a49cfd96e90116fffcd5c4: Bug 1632171 [wpt PR 23168] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 23 Apr 2020 01:12:07 +0000 - rev 590712
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632171 [wpt PR 23168] - Update wpt metadata, a=testonly wpt-pr: 23168 wpt-type: metadata
9eaceb35934a3104c58890e409bc5a79891c4994: Bug 1632171 [wpt PR 23168] - [@property] Mark for recalc when removing declarations, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Tue, 28 Apr 2020 11:38:58 +0000 - rev 590711
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632171 [wpt PR 23168] - [@property] Mark for recalc when removing declarations, a=testonly Automatic update from web-platform-tests [@property] Mark for recalc when removing declarations I forgot to notify StyleEngine when the property registry changes due to declarations being cleared. This meant removals would not take effect correctly/predictably. Since CSS.registerProperty / @property use the pattern of static methods on PropertyRegistration to do some work + notifying StyleEngine, we can follow the same pattern for this case. Also rename CustomPropertyRegistered to PropertyRegistryChanged. Bug: 978780, 973830 Change-Id: I3bd03f548a7783f1270d823501e4bf9b1c0778e6 -- wpt-commits: cd987667984a6d28c51e6335535c3e585c7e4ee1 wpt-pr: 23168
779273edaf951bb453327d31c839fa0587bfa70e: Bug 1633704 [wpt PR 23087] - [server-timing] Populate values for NavigationTiming, a=testonly
Yoav Weiss <yoavweiss@chromium.org> - Tue, 28 Apr 2020 11:38:53 +0000 - rev 590710
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1633704 [wpt PR 23087] - [server-timing] Populate values for NavigationTiming, a=testonly Automatic update from web-platform-tests [server-timing] Populate values for NavigationTiming Currently, Navigation Timing's Server Timing values are populated when the entry is first created, which happens when it is first queried. For long documents, that can happen before the body is loaded, which is the point in which the response is set on the NavigationTiming entry's TimingInfo. This CL fixes that, by setting the response on the TimingInfo earlier, at the document's commit time. Change-Id: I10522342a7d92560167bdb7d33956823e588d9d8 Bug: 1068937 Change-Id: I10522342a7d92560167bdb7d33956823e588d9d8 -- wpt-commits: 0084aa71d4d4935fcbb43bd8122328da9d305098 wpt-pr: 23087
d49a0349f0bc8108fa05bcfd6e2e11536f13f44e: Bug 1631985 [wpt PR 23158] - Correct input connection and automatic pull behavior of AudioWorkletNode, a=testonly
Hongchan Choi <hongchan@chromium.org> - Tue, 28 Apr 2020 11:38:48 +0000 - rev 590709
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1631985 [wpt PR 23158] - Correct input connection and automatic pull behavior of AudioWorkletNode, a=testonly Automatic update from web-platform-tests Correct input connection and automatic pull behavior of AudioWorkletNode This CL fixes a failing test (process-parameters.https.html) and it needs two changes in AudioWorkletNode: 1. Handling of unconnected inputs: - spec: https://webaudio.github.io/web-audio-api/#dom-audioworkletprocessor-process-inputs-outputs-parameters-inputs - "If there are no actively processing AudioNodes connected to the 𝑛th input of the AudioWorkletNode for the current render quantum, then the content of inputs[n] is an empty array, indicating that zero channels of input are available." - Thus, if an input is not connected, it will have an array with zero element. (length == 0) 2. Handling of automatic pull: - The implementation did not have a proper automatic pull functionality for AudioWorkletNode. Without connect() or disconnect() call the node will not be automatically pulled. This change introduces failures in the "active processing" tests, because those tests are expecting non-zero channel count for the unconnected input: - the-audiobuffersourcenode-interface/active-processing.https.html - the-channelmergernode-interface/active-processing.https.html - the-convolvernode-interface/active-processing.https.html I prefer to mark 3 tests above "failure", and handle them later in a separate patch. Bug: 1046516 Test: the-audioworklet-interface/process-parameters.https.html Change-Id: I55f9a1b6eb88c172a8d050598c6e5f946fe9692b -- wpt-commits: e764b34bd01c8ed11efeb9205589dc4dbf09cf54 wpt-pr: 23158
6a349c347319b561cadc1907b672494a1c4fbd7f: Bug 1632253 [wpt PR 23180] - Reland "[EventTiming] Add shadow DOM test for first input", a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Tue, 28 Apr 2020 11:38:38 +0000 - rev 590708
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632253 [wpt PR 23180] - Reland "[EventTiming] Add shadow DOM test for first input", a=testonly Automatic update from web-platform-tests Reland "[EventTiming] Add shadow DOM test for first input" This is a reland of 9591b7074cacf1e8aeb9082dee2a4f46a171083f Original change's description: > [EventTiming] Add shadow DOM test for first input > > This CL tests event.target for first-input. The DOM elements do not have > event listeners to show that event retargetting correctly retargets to > the shadow host. > > Bug: 543598 > Change-Id: Ibd5a4a37a50f79b86d93a5c9c18c8ac7300ba723 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159622 > Reviewed-by: Steve Kobes <skobes@chromium.org> > Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#761417} Bug: 543598 Change-Id: I21537ddc47075a5f0acaf0b53662b4db242c66a0 -- wpt-commits: 2a3389554f038ed396be6f699414aad23e7fe581 wpt-pr: 23180
f640897b7f647d42ce7a96fa0f6544e4e32466a8: Bug 1632172 [wpt PR 23169] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Apr 2020 22:00:56 +0000 - rev 590707
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632172 [wpt PR 23169] - Update wpt metadata, a=testonly wpt-pr: 23169 wpt-type: metadata
8236f2312205f36c98f552c353b6ebebf9c91d58: Bug 1632172 [wpt PR 23169] - [@property] Initial should be required for non-universal syntax, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Tue, 28 Apr 2020 11:38:23 +0000 - rev 590706
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632172 [wpt PR 23169] - [@property] Initial should be required for non-universal syntax, a=testonly Automatic update from web-platform-tests [@property] Initial should be required for non-universal syntax - Require an initial value for the @property rule to be valid. (Except universal syntax definitions). - Rename IsTokenStream -> IsUniversal. (It's nice to have names that match the spec concepts). - Fix typo 'initalValue' in an otherwise unrelated test. Bug: 973830 Change-Id: I675f0c46b7918e4a81287d600d977ff76484cf8b -- wpt-commits: 959a0d091354d3cb78d71c00a418092f29ce9857 wpt-pr: 23169
51094411f8151fa202592bd29ae81ba7fd857534: Bug 1632174 [wpt PR 23170] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Apr 2020 21:33:50 +0000 - rev 590705
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632174 [wpt PR 23170] - Update wpt metadata, a=testonly wpt-pr: 23170 wpt-type: metadata
e7e2d87f4e19cbfada8ba23fdfb8cd37ad933243: Bug 1632174 [wpt PR 23170] - css-flexbox: convert 7 manual-tests to ref-tests, a=testonly
Carlos Alberto Lopez Perez <clopez@igalia.com> - Tue, 28 Apr 2020 11:38:15 +0000 - rev 590704
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632174 [wpt PR 23170] - css-flexbox: convert 7 manual-tests to ref-tests, a=testonly Automatic update from web-platform-tests css-flexbox: convert 7 manual-tests to ref-tests (#23170) * This converts the css-flexbox align-content_*.html tests and flexbox-order-only-flexitems.html test to ref-tests. * css-flexbox/align-content_space-around.html change height to 210: that way the numbers of the ref-test spacer become 20 and 10 and are perfectly round avoiding possible problems with subpixel layout. -- wpt-commits: b3cc52b6cfaa5b6852bf9b07e62d007ab142ffa9 wpt-pr: 23170
28c38e708ee70cf00c07111f3f222a12ecb4b3a9: Bug 1632238 [wpt PR 23178] - [FlexNG] Add test for replaced %-block-size descendant., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Tue, 28 Apr 2020 11:38:10 +0000 - rev 590703
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632238 [wpt PR 23178] - [FlexNG] Add test for replaced %-block-size descendant., a=testonly Automatic update from web-platform-tests [FlexNG] Add test for replaced %-block-size descendant. With FlexNG we now cache on the ComputeMinMaxSizes level. This fixes a subtle dynamic edge case. Previously (legacy) wouldn't invalidate the flex-item base size due to a parent height changes. This adds a test for this case. Bug: 845235 Change-Id: Ic711c3f8110b08fcc89351274a7bd283f66c1ce1 -- wpt-commits: 9eb7edb448e51c8c3e024608484290f19f374415 wpt-pr: 23178
22b4c441833ad87045e70368fc949cadf282a844: Bug 1632230 [wpt PR 23175] - Sort CSS computed style properties in lexicographical order, again, a=testonly
Oriol Brufau <obrufau@igalia.com> - Tue, 28 Apr 2020 11:38:05 +0000 - rev 590702
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632230 [wpt PR 23175] - Sort CSS computed style properties in lexicographical order, again, a=testonly Automatic update from web-platform-tests Sort CSS computed style properties in lexicographical order, again This is a follow-up of r760732, where I included logical properties when iterating a computed style declaration. The problem was that I inserted some of them at the wrong position, breaking the lexicographical order achieved in r760690. This time I add a test that checks that the order is right. BUG=1072722,1072180 TEST=external/wpt/css/cssom/cssstyledeclaration-csstext.html TEST=external/wpt/css/cssom/getComputedStyle-property-order.html Change-Id: I3ea31024deed8b5a4c67a5a117c358cab6c9d7d4 -- wpt-commits: dbe025b0ce82a78a68bf63e7f657615378cbcb39 wpt-pr: 23175
77f5099ba866706a81710a03003e68fa74ce64e9: Bug 1632106 [wpt PR 23166] - Add support for canceling CSS transitions, a=testonly
Martin Robinson <mrobinson@igalia.com> - Tue, 28 Apr 2020 11:38:00 +0000 - rev 590701
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1632106 [wpt PR 23166] - Add support for canceling CSS transitions, a=testonly Automatic update from web-platform-tests Add support for canceling CSS transitions This change adds support for canceling CSS transitions when a property is no longer transitionable or when an element becomes styled with display:none. Support for canceling and replacing CSS transitions when the end value changes is still pending. This change also takes advantage of updating the constellation message to fix a bug where transition events could be sent for closed pipelines. Fixes #15079. -- wpt-commits: 7c3ddf7343d1577cd5279fb132a17617feeebfe3 wpt-pr: 23166
6e66a836862011807043a8a8c31b5138538b0e2a: Bug 1630540 [wpt PR 22994] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Apr 2020 20:34:57 +0000 - rev 590700
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1630540 [wpt PR 22994] - Update wpt metadata, a=testonly wpt-pr: 22994 wpt-type: metadata
d6ebb1b3f1e4da30122ff44855741a7fb28ce8bb: Bug 1630540 [wpt PR 22994] - DedicatedWorker: Refine WPTs to test parse error handling, a=testonly
Eriko Kurimoto <elkurin@chromium.org> - Tue, 28 Apr 2020 11:37:53 +0000 - rev 590699
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1630540 [wpt PR 22994] - DedicatedWorker: Refine WPTs to test parse error handling, a=testonly Automatic update from web-platform-tests DedicatedWorker: Refine WPTs to test parse error handling This CL modifies web-platform-test for parse error handling in classic and module dedicated workers. This CL does followings: 1. Divide workers/modules/dedicated-worker-parse-error-failure.html into the tests for classic workers and for module workers. 2. For module workers, check if module script is supported before testing parse error handling. 3. Check the content of the dispatched event. This change is based on WPTs for shared workers parse error handling. Bug: 1071345 Change-Id: I738c89d5241a94df17092a3b106b5b795a26a7de -- wpt-commits: f6f6077aab9fea53099084cd009e0701ca5dcfa7 wpt-pr: 22994
4147a555fd8fd82234e1eba58b6a333d250b1c58: Bug 1631356 [wpt PR 23105] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Apr 2020 19:39:24 +0000 - rev 590698
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1631356 [wpt PR 23105] - Update wpt metadata, a=testonly wpt-pr: 23105 wpt-type: metadata
a1a73fefe890d9fd377e15fcac599508ea28e1c1: Bug 1631356 [wpt PR 23105] - ServiceWorker: Fix timeout on client-navigate.https.html, a=testonly
Hiroki Nakagawa <nhiroki@chromium.org> - Tue, 28 Apr 2020 11:37:45 +0000 - rev 590697
Push 13072 by ffxbld-merge at Mon, 04 May 2020 14:22:08 +0000
Bug 1631356 [wpt PR 23105] - ServiceWorker: Fix timeout on client-navigate.https.html, a=testonly Automatic update from web-platform-tests ServiceWorker: Fix timeout on client-navigate.https.html This CL fixes timeout on client-navigate.https.html, and removes unused code in testharness.js. This change is a follow-up for: [1] https://github.com/web-platform-tests/wpt/pull/21162 [2] https://github.com/web-platform-tests/wpt/pull/22086 After the change [1], fetch_tests_from_workers() helper uses ExtendableMessageEvent.source instead of MessageChannel to communicate between a window and a service worker. This change works well for most of cases, but fails some tests. The fetch_tests_from_workers() helper takes a service worker object to post a "connect" message to the worker, and then passes the worker object to RemoteContext in testharness.js. RemoteContext adds an onmessage event handler on self.navigator.serviceWorker. This works well as long as the given worker object is associated with `self`. However, these failing tests pass the worker object associated with the inner frame to the helper. In this case, the helper uses an inner frame's service worker object for postMessage(), while the helper waits on the main frame's navigator.serviceWorker.onmessage. Consequently event.source is the inner frame, and a reply from the service worker is dispatched on the inner frame's navigator.serviceWorker.onmessage. This results in timeout. To fix this, this CL makes the main frame pass its own service worker object instead of the inner frame's service worker object. Those objects should be equal other than associated contexts, and this change doesn't affect what the tests verify. Bug: 1057682 Change-Id: I0f30f1fe9c54c3de1006276f3445c5e2b92ea5a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155760 Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#760974} -- wpt-commits: 0a9ee5f5458c922aab15c25339db79e93df5c707 wpt-pr: 23105
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip