ec6d4d042778ae8d8d00c8b3ddeca04f5dd99824: 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 527588
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
0b423a6d0e95349c5ff9d424c71c9174fd86203b: 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 527587
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
2ff1de7ecca0db42609d6dd2d8830144af422777: 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 527586
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632172 [wpt PR 23169] - Update wpt metadata, a=testonly wpt-pr: 23169 wpt-type: metadata
7fe7d0cc8de424784479a0702abba7edc306d957: 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 527585
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
c3b71a950a5bc8e076c8319dc08491313d4968e1: 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 527584
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632174 [wpt PR 23170] - Update wpt metadata, a=testonly wpt-pr: 23170 wpt-type: metadata
e3fce10d86ae39772ccfa831e0fd0d726e2165f3: 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 527583
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
2452c37111886680e246b04e30d0055d011e240c: 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 527582
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
c5443e2f9b7ce635d6dbac63e58486cf27a46609: 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 527581
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
c0bc5e2f0949fa1e86fad7e522f05c37a84dfdc2: 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 527580
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
99abccb00c35e87ee213a206b75c9bb9558eaa30: 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 527579
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1630540 [wpt PR 22994] - Update wpt metadata, a=testonly wpt-pr: 22994 wpt-type: metadata
175fd05289e15654205f9cd95a2ad89c6caa4649: 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 527578
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
c810496118ef82f0f29650c7deebfda23ab36ea9: 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 527577
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631356 [wpt PR 23105] - Update wpt metadata, a=testonly wpt-pr: 23105 wpt-type: metadata
e4f2dd72c208f41d4cccb483eeead7523e60e0fc: 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 527576
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +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
4cdada5d87dffd05db728efe8e1c5d43bc6cd7f8: Bug 1631923 [wpt PR 23151] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Apr 2020 19:36:29 +0000 - rev 527575
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631923 [wpt PR 23151] - Update wpt metadata, a=testonly wpt-pr: 23151 wpt-type: metadata
fb45c867b69d09c119cf38ccdcd0844066d4ebf8: Bug 1631923 [wpt PR 23151] - Migrate pointerevents/touch-pointercancel.html to wpt, a=testonly
Navid Zolghadr <nzolghadr@chromium.org> - Tue, 28 Apr 2020 11:37:27 +0000 - rev 527574
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631923 [wpt PR 23151] - Migrate pointerevents/touch-pointercancel.html to wpt, a=testonly Automatic update from web-platform-tests Migrate pointerevents/touch-pointercancel.html to wpt pointerevents/touch-pointercancel.html test verifies the touch and pointer events interaction in single and multi touch point cases when scrolling happens or not. The single touch point portion is already tested as part of wpt/pointerevents/pointerevent_pointercancel_touch.html The two finger interaction is not very well specified and is tested as part of wpt/pointerevents/compat/pointerevent_touch-action_two-finger_interaction.html and that only is missing the pointerid checks that this CL adds as well. Change-Id: I3ee27866dddc02cb87b1082b5a4fe2f9e8ba9220 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159577 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#761123} -- wpt-commits: eec9d65928b85f2ab8dc5252deb128d2246994af wpt-pr: 23151
ed97836553af5bc29989d8e941f331cf956394e7: Bug 1630628 [wpt PR 23007] - Replace assert_precondition with assert_equals in domparsing/, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:37:22 +0000 - rev 527573
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1630628 [wpt PR 23007] - Replace assert_precondition with assert_equals in domparsing/, a=testonly Automatic update from web-platform-tests Replace assert_precondition with assert_equals in domparsing/ (#23007) assert_precondition is deprecated (see https://github.com/web-platform-tests/rfcs/blob/master/rfcs/assert_precondition_rename.md). In this particular case, the assertion is actually checking for an equality rather than an 'implements' phrase, so switch to assert_equals. -- wpt-commits: e65087045387dd4ecb9d5c675062a6643e00c7ad wpt-pr: 23007
d999146c5b07bcc326ee8f88a9fea0a5dd988405: Bug 1633435 [wpt PR 23173] - Revert "[EventTiming] Add shadow DOM test for first input", a=testonly
Elly Fong-Jones <ellyjones@chromium.org> - Tue, 28 Apr 2020 11:37:15 +0000 - rev 527572
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1633435 [wpt PR 23173] - Revert "[EventTiming] Add shadow DOM test for first input", a=testonly Automatic update from web-platform-tests Revert "[EventTiming] Add shadow DOM test for first input" This reverts commit 9591b7074cacf1e8aeb9082dee2a4f46a171083f. Reason for revert: Failed blink_web_tests on webkit linux leak: https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Linux%20Leak/13490: ({"numberOfLiveContextLifecycleStateObservers":[2,5],"numberOfLiveDocuments":[1,2],"numberOfLiveNodes":[4,21],"numberOfLiveResourceFetchers":[1,2],"numberOfLiveResources":[0,4]}) 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} TBR=skobes@chromium.org,npm@chromium.org Change-Id: I941e3f093e3d1fcba6662a54dec51b66690c9d70 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 543598 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161125 Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#761446} -- wpt-commits: b0e8930b6ed1b39a4bb9341a772b4efbc9ccb5f6 wpt-pr: 23173
486df864d8d4a36a5a3b6d4e8951c7db2ad6a039: Bug 1632190 [wpt PR 23171] - Add MathML tests for color/visibility of normal, large and stretchy mo., a=testonly
Frédéric Wang <fwang@igalia.com> - Tue, 28 Apr 2020 11:37:10 +0000 - rev 527571
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632190 [wpt PR 23171] - Add MathML tests for color/visibility of normal, large and stretchy mo., a=testonly Automatic update from web-platform-tests Add MathML tests for color/visibility of normal, large and stretchy mo. (#23171) https://github.com/mathml-refresh/mathml/issues/57 -- wpt-commits: 4338d5203d020abe7249f34f93dc170c32c23dfa wpt-pr: 23171
46ecf7e8fcfcfcd7073bdc2cf812fd10cf27fd86: Bug 1632044 [wpt PR 23164] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 27 Apr 2020 10:34:14 +0000 - rev 527570
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632044 [wpt PR 23164] - Update wpt metadata, a=testonly wpt-pr: 23164 wpt-type: metadata
3a312842c93cb4177df2d959979dff57a587043b: Bug 1632044 [wpt PR 23164] - XHR: align with Fetch's Content-Type stripping, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 28 Apr 2020 11:37:02 +0000 - rev 527569
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632044 [wpt PR 23164] - XHR: align with Fetch's Content-Type stripping, a=testonly Automatic update from web-platform-tests XHR: align with Fetch's Content-Type stripping Also modernize the code a tiny bit. Closes #23156. -- wpt-commits: 79311e3ce537612a80c21afc0013ee074d1fc5c1 wpt-pr: 23164
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip