87c14a52fe48b08d18d3227c8476a102de8bec86: Bug 1717407 [wpt PR 29439] - Update wpt/webrtc/protocol/README.txt with RFC numbers, a=testonly
Harald Alvestrand <hta@chromium.org> - Fri, 25 Jun 2021 22:13:03 +0000 - rev 652893
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717407 [wpt PR 29439] - Update wpt/webrtc/protocol/README.txt with RFC numbers, a=testonly Automatic update from web-platform-tests Update wpt/webrtc/protocol/README.txt with RFC numbers Bug: none Change-Id: I0394d26730b35e09d6010af32bab9d2b00a1614a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2972587 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#894192} -- wpt-commits: 113a5aeccba137b80e3f37a9bda82967d0138682 wpt-pr: 29439
f577a605e9aa677c02dcb47e9b997372d318e385: Bug 1716263 [wpt PR 29356] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 19 Jun 2021 09:12:36 +0000 - rev 652892
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716263 [wpt PR 29356] - Update wpt metadata, a=testonly wpt-pr: 29356 wpt-type: metadata
0a1af82c3cd7ba22732bbf9e327cb6a6f254b40b: Bug 1716263 [wpt PR 29356] - Supports all ':has' relative argument cases, a=testonly
Byungwoo Lee <blee@igalia.com> - Fri, 25 Jun 2021 22:12:52 +0000 - rev 652891
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716263 [wpt PR 29356] - Supports all ':has' relative argument cases, a=testonly Automatic update from web-platform-tests Supports all ':has' relative argument cases Currently the relative selector is not supported yet, so this CL provides the relative argument cases as follows. - :has(:scope > <complex-selector>) - :has(:scope ~ <complex-selector>) - :has(:scope + <complex-selector>) This CL provides a wpt test for the above usage. - has-relative-argument.html While matching those argument selectors on the :has argument subtree of an element, we can get the candidate scope elements. By marking those elements as matched, we can reduce the duplicated ':has' argument matching operation. HasArgumentSubtreeIterator provides the way to traverse the ':has' argument subtree (downward subtree of the :has scope element). The iterator provides right-to-left post-order traversal to prevent incorrect 'NotMatched' status. And it also provides a way to limit traversal depth or adjacent distance to prevent unnecessary tree traversal for direct relations (child/direct sibling). About the issue of incorrect 'NotMatched' status, the previous caching logic has a bug of incorrectly using the cached status to skip one argument selector matching operation for one descendant of an element. The cached status should be used to skip the argument matching operations for all the descendants of an element because it is the status of :has scope element. To store the 'NotMatched' status correctly during the ':has' subtree traversal for argument selector matching , the traversal order should be right-to-left reversed post-order to guarantee that, the downward subtree(descendants/next siblings/descendants of next siblings) of an element was checked with the argument selector before checking the element and the previous check didn't mark the element as 'Matched'. The ':has(.descendant)' test case in the 'has-basic.html' missed to have an expected return value related with this bug, so the test result is fixed with this CL. And to check the added/fixed logic, following test are added. - has-relative-argument.html Change-Id: I71f8752ad90d32c6f9ee6bf87949b838e3843eba Bug: 669058 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2914967 Commit-Queue: Byungwoo Lee <blee@igalia.com> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#894067} -- wpt-commits: eff766e5c8c39be7b9bff064bce3a18eb2953ac5 wpt-pr: 29356
136c0fe36862d59b4bcd953ef538c1fc5fcdc813: Bug 1716013 [wpt PR 29345] - [composite-bgcolor-animation] Return empty result when PaintWorkletInput not found, a=testonly
Xida Chen <xidachen@chromium.org> - Fri, 25 Jun 2021 22:12:47 +0000 - rev 652890
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716013 [wpt PR 29345] - [composite-bgcolor-animation] Return empty result when PaintWorkletInput not found, a=testonly Automatic update from web-platform-tests [composite-bgcolor-animation] Return empty result when PaintWorkletInput not found The root cause of the problem is that there is an early exit in the DiscardableImageMap::GatherDiscardableImages(), happening when the paint rect for the op is empty. This makes sense because there is nothing to draw. Note that this is different than the empty element case. In fact, we already have "background-color-animation-zero-size-element.html" under css-backgrounds/animations/ and there is no problem with that. The bug happens when the element is not empty, but its intersection with the SkCanvas that it draws into is empty. Please see the notes in this doc for more details: https://docs.google.com/document/d/1Da9d7ai5xt4nPX7NDZnqaaTSoFitRSeYxw1qxGjtdeQ/edit The |PaintWorkletImageProvider::records_| contains the records for all the discardable images that can draw. Meaning that the ones that early exits won't be included in the |records_|. But, when the PaintWorkletImageProvider::GetPaintRecordResult() is called, the input parameter |PaintWorkletInput| would contain all possible PaintWorkletInput that is passed from Blink to CC, which obviously contains the ones that cannot draw. As a result, these PaintWorkletInputs won't exists in the |records_|. We handle these cases by returning an empty record because there is nothing to draw (like empty container cases). Bug: 1216210 Change-Id: I9630aa4b55fd1322f641f42b05c20aab8c7234c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2954479 Reviewed-by: Philip Rogers <pdr@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#894050} -- wpt-commits: 4c83511984d28d692a68de2330a844183b9d488e wpt-pr: 29345
6d44f44c9acb07f4939d67a27261e689ae47d9dc: Bug 1717244 [wpt PR 29435] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 18 Jun 2021 22:51:52 +0000 - rev 652889
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717244 [wpt PR 29435] - Update wpt metadata, a=testonly wpt-pr: 29435 wpt-type: metadata
3a5667e5d8aaba2e5224890548c8318d649dc4ab: Bug 1717244 [wpt PR 29435] - [GridNG] Fix expectations for align and justify self abspos img tests, a=testonly
Ana SollanoKim <ansollan@microsoft.com> - Fri, 25 Jun 2021 22:12:39 +0000 - rev 652888
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717244 [wpt PR 29435] - [GridNG] Fix expectations for align and justify self abspos img tests, a=testonly Automatic update from web-platform-tests [GridNG] Fix expectations for align and justify self abspos img tests Similar to the issue fixed in https://chromium-review.googlesource.com/c/chromium/src/+/2860338/. The references of 2 web tests were modified to account for border, scrollbar and padding of the grid. Bug: 1045599 Change-Id: Id0f5f6b71bc0bda8892135d2bec323c950797dc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2973510 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#893981} -- wpt-commits: 291466f507f4d91b7e2f04da088163576b7349ef wpt-pr: 29435
dd4d823760a0821452fc2d3e642ead393e7fafef: Bug 1716372 [wpt PR 29364] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 18 Jun 2021 20:03:50 +0000 - rev 652887
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716372 [wpt PR 29364] - Update wpt metadata, a=testonly wpt-pr: 29364 wpt-type: metadata
37816e1ec3d7025467dafc5763212554f46485a9: Bug 1716372 [wpt PR 29364] - [ResourceTiming]: Extend TAO-match.html test to cover more resource types, a=testonly
Tom McKee <tommckee@chromium.org> - Fri, 25 Jun 2021 22:12:29 +0000 - rev 652886
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716372 [wpt PR 29364] - [ResourceTiming]: Extend TAO-match.html test to cover more resource types, a=testonly Automatic update from web-platform-tests [ResourceTiming]: Extend TAO-match.html test to cover more resource types Since we have different code paths for loading different types of resources, this CL adds tests for Timing-Allow-Origin parsing/checking that exercise more resource types than before. This test is actually failing right now for Chrome but should pass in other browsers. Part of the reason to land this now is to see if other browsers will need fixes too. Bug: 1218565 Change-Id: Id274ec1fd914f62d3b805d4d69f81f2945a8baaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2956309 Commit-Queue: Tom McKee <tommckee@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#893912} -- wpt-commits: 8a1c240d0fcb7c965e79222225d7aa653376d783 wpt-pr: 29364
f8f00739dd5ae3760a297d32fde8dfe8e1dab97a: Bug 1717098 [wpt PR 29422] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 18 Jun 2021 18:43:34 +0000 - rev 652885
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717098 [wpt PR 29422] - Update wpt metadata, a=testonly wpt-pr: 29422 wpt-type: metadata
097d4ba7ab65a4969ab78e6e2d23141d457531eb: Bug 1717098 [wpt PR 29422] - Replace unpaired surrogates after evaluating javascript URLs, a=testonly
Timothy Gu <timothygu@chromium.org> - Fri, 25 Jun 2021 22:12:21 +0000 - rev 652884
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717098 [wpt PR 29422] - Replace unpaired surrogates after evaluating javascript URLs, a=testonly Automatic update from web-platform-tests Replace unpaired surrogates after evaluating javascript URLs Given a URL like javascript:String.fromCodePoint(0xDE0D), Chrome currently displays three U+FFFD replacement characters rather than just one, due to the incorrect UTF-8 conversion mode. We fix that by using kStrictUTF8ConversionReplacingUnpairedSurrogatesWithFFFD. This CL fully implements https://github.com/whatwg/html/pull/6781. Tests are partially taken from https://github.com/web-platform-tests/wpt/pull/29419. Co-authored-by: Domenic Denicola <domenic@chromium.org> Bug: 1221018 Change-Id: Ic1282d0a88eabb40b4d5d8d8c68e040e9a0a938d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2967353 Commit-Queue: Timothy Gu <timothygu@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#893876} -- wpt-commits: ad7af3947f19693e8ab8911663a41152e907ed0e wpt-pr: 29422
f082ac3eb53dc021639c8538eb78f36491718c90: Bug 1716995 [wpt PR 29413] - Don't ignore parent frame during UpdateStyleAndLayoutTreeForNode, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Fri, 25 Jun 2021 22:12:16 +0000 - rev 652883
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716995 [wpt PR 29413] - Don't ignore parent frame during UpdateStyleAndLayoutTreeForNode, a=testonly Automatic update from web-platform-tests Don't ignore parent frame during UpdateStyleAndLayoutTreeForNode We would incorrectly behave as if were were style-clean if an outer frame was dirtied with an inner media query. This causes getAnimations (and probably other cases) to report the wrong thing. Note: The provided test passes in Firefox. Change-Id: Ia0743f775804463fb4cf98cce2be013f44ee6c87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2968003 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#893776} -- wpt-commits: b3f866edc8969fb7a8b452364411864d56e23e18 wpt-pr: 29413
4d5153eb7982893d42419e4d085bc15b0e208869: Bug 1716969 [wpt PR 29410] - [Credentialless] Fix flaky COEP:credentialless reporting navigation test, a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Fri, 25 Jun 2021 22:12:12 +0000 - rev 652882
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716969 [wpt PR 29410] - [Credentialless] Fix flaky COEP:credentialless reporting navigation test, a=testonly Automatic update from web-platform-tests [Credentialless] Fix flaky COEP:credentialless reporting navigation test While running tests repeatedly and parallel, the reports may not be received within the time delay. This CL wait for expected number of reports and wait 500ms more for unexpected reports to avoid the previous situation. Bug: 1218372, 1218484 Change-Id: Ideadcffa4ad7de86ccfbc053f3d212951a136eb7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2964531 Reviewed-by: Yifan Luo <lyf@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Yifan Luo <lyf@chromium.org> Cr-Commit-Position: refs/heads/master@{#893717} -- wpt-commits: b7ea86c5012703a698f90311bc630b4798c46ac9 wpt-pr: 29410
682f70e60286e291d4bb455b32a3cea835d0bd74: Bug 1716732 [wpt PR 29397] - Move out the rendered legend box from the anonymous fieldset content box., a=testonly
Kent Tamura <tkent@chromium.org> - Fri, 25 Jun 2021 22:12:07 +0000 - rev 652881
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716732 [wpt PR 29397] - Move out the rendered legend box from the anonymous fieldset content box., a=testonly Automatic update from web-platform-tests Move out the rendered legend box from the anonymous fieldset content box. This is based on https://chromium-review.googlesource.com/c/chromium/src/+/2336563/8 We had a rendered legend box as a child of an anonymous fieldset content box, and had adjustment code at many places. This CL updates this structure so that the rendered legend box is a child of the fieldset box as the specification asks. The main change is LayoutNGFieldset::AddChild(). If the rendered legend is passed to this function, it is added as a child of the fieldset, not a child of the anonymous fieldset content box. Because the rendered legend depends on some CSS properties and the order of children, we need to reattach a fieldset to keep the correct LayoutObject structure: * ComputedStyle::NeedsReattachLayoutTree() Trigger reattach of a legend if its 'position' or 'float' properties are changed: * HTMLFieldSetElement::DidRecalcStyle() Trigger reattach of a fieldset if any child box is reattached. * HTMLLegendElement::DetachLayoutTree() Trigger reattach of a fieldset if a rendered LEGEND is detached. Test changes: * display-contents-dynamic-fieldset-legend-001.html Add testcases of adding a rendered legend to a display:contents element, and removing a rendered legend from a display:contents element. * fieldset-content-before-legend.html and fieldset-generated-content.html They are updated so that they are not affected by fractional paddings and fractional letter widths. * fieldset-content-before-legend.html Added a testcase for DCHECK(!before_child) in AddChild(). * NGFieldsetLayoutAlgorithmTest Many test cases now have no anonymous fieldset content boxes. Bug: 880062, 1214561 Change-Id: I45a6b4eb1dcb1f3c3ab052324c3839c0d9a85b3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2960239 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#893709} -- wpt-commits: ac3c841a788f9f3784a0774c00911fbe2219260f wpt-pr: 29397
4f222d7066750e25322f46902c66cd97ac31e099: Bug 1716669 [wpt PR 29392] - [css-align-3][css-grid-1][css-flexbox-1] Add tests for safe/unsafe alignment keywords., a=testonly
fantasai <fantasai.bugs@inkedblade.net> - Fri, 25 Jun 2021 22:12:00 +0000 - rev 652880
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1716669 [wpt PR 29392] - [css-align-3][css-grid-1][css-flexbox-1] Add tests for safe/unsafe alignment keywords., a=testonly Automatic update from web-platform-tests [css-align-3][css-grid-1][css-flexbox-1] Add tests for safe/unsafe alignment keywords. -- wpt-commits: 07406d022f7bb6620176db9f7fb7fbbe559567f1 wpt-pr: 29392
38341981d24a19806a0bc49dbc9c9aec3a278f2e: Bug 1717087 [wpt PR 29420] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 18 Jun 2021 02:03:53 +0000 - rev 652879
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717087 [wpt PR 29420] - Update wpt metadata, a=testonly wpt-pr: 29420 wpt-type: metadata
200a67f626476ed0ad4a6329afcf4d79d66b1990: Bug 1717087 [wpt PR 29420] - URLPattern: Remove [SecureContext] requirement., a=testonly
Ben Kelly <wanderview@chromium.org> - Fri, 25 Jun 2021 22:11:49 +0000 - rev 652878
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717087 [wpt PR 29420] - URLPattern: Remove [SecureContext] requirement., a=testonly Automatic update from web-platform-tests URLPattern: Remove [SecureContext] requirement. Many new, powerful APIs require [SecureContext] as a carrot for developers to adopt https. This is effective because its not possible for sites to otherwise provide the features provided by those APIs. In this case, however, URLPattern can largely be polyfilled in javascript. Restricting the API to [SecureContext] offers no leverage to convince developers to adopt https because they can simply include the polyfill. Instead, the negatives of this restriction simply accrue to the user who must pay the cost of downloading and executing the additional javascript resources. Therefore this CL removes the [SecureContext] requirement as its not effective for this API. Bug: 1141510 Change-Id: I2714a9292d9002c49ee9b09a6ca12b26cff63614 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2968793 Reviewed-by: Jeremy Roman <jbroman@chromium.org> Commit-Queue: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#893634} -- wpt-commits: 5769c1a8e58edae508d48827b519c5a127dedff4 wpt-pr: 29420
684af5bce891c0996acd56d81c69c5f5a34f1e57: Bug 1717094 [wpt PR 29421] - [css-scroll-anchoring] Add another test with abspos and multicol, a=testonly
Oriol Brufau <obrufau@igalia.com> - Fri, 25 Jun 2021 22:11:43 +0000 - rev 652877
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717094 [wpt PR 29421] - [css-scroll-anchoring] Add another test with abspos and multicol, a=testonly Automatic update from web-platform-tests [css-scroll-anchoring] Add another test with abspos and multicol This test is similar to the one added in r889310, and used to fail with --enable-blink-features=LayoutNGBlockFragmentation The difference is that this one passes after r891351. Bug: 1216165 Change-Id: I7dcec01578338dc42f6a9333f118de03fe64ef48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2970583 Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#893589} -- wpt-commits: 090ef15f016538bab2955bcc34f1dd98267a3033 wpt-pr: 29421
e7b53af997311db7aff91c40c796cd0a8320cd43: Bug 1717120 [wpt PR 29407] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 18 Jun 2021 08:41:06 +0000 - rev 652876
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717120 [wpt PR 29407] - Update wpt metadata, a=testonly wpt-pr: 29407 wpt-type: metadata
bf020f8ff2aa47219a5ee63723f531f89af4f8ef: Bug 1717120 [wpt PR 29407] - [webcodecs] Create RGBA frames when alpha=keep., a=testonly
Dan Sanders <sandersd@chromium.org> - Fri, 25 Jun 2021 22:11:34 +0000 - rev 652875
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717120 [wpt PR 29407] - [webcodecs] Create RGBA frames when alpha=keep., a=testonly Automatic update from web-platform-tests [webcodecs] Create RGBA frames when alpha=keep. Bug: 1138681 Change-Id: Ib4dc9e607cf207947d9e948fde7b3776d4cb40c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2965145 Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#893550} -- wpt-commits: 81174d613348dc00171362ee55fcccefddc7e738 wpt-pr: 29407
557f3c64b599af6ae5439821df6d90de8fba1fc0: Bug 1717017 [wpt PR 29415] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 17 Jun 2021 20:16:45 +0000 - rev 652874
Push 15597 by ffxbld-merge at Mon, 12 Jul 2021 12:28:04 +0000
Bug 1717017 [wpt PR 29415] - Update wpt metadata, a=testonly wpt-pr: 29415 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip