ec00533cc6dc2b3ef1f0a3206df8cbf376354d10: Bug 1636134 [wpt PR 23462] - webrtc wpt: merge simulcast getStats tests, a=testonly
Philipp Hancke <philipp.hancke@googlemail.com> - Wed, 13 May 2020 09:46:29 +0000 - rev 594883
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636134 [wpt PR 23462] - webrtc wpt: merge simulcast getStats tests, a=testonly Automatic update from web-platform-tests webrtc wpt: merge simulcast getStats tests merges the simulcast getStats test into a single test. Waiting for simulcast ramp-up twice takes too long and is flaky BUG=chromium:1077194 Change-Id: I42c11ccc76c5cf52fc3a7596a5a13cdaf3817623 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2187374 Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#766431} -- wpt-commits: c390f441840c65b55f014a34ef0459853709286b wpt-pr: 23462
d9927e35fbdf0ed9b1b50ae67ce33cf3fd20b453: Bug 1636020 [wpt PR 23450] - Correct context for paint properties for out-of-flow under multicol, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Wed, 13 May 2020 09:46:24 +0000 - rev 594882
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636020 [wpt PR 23450] - Correct context for paint properties for out-of-flow under multicol, a=testonly Automatic update from web-platform-tests Correct context for paint properties for out-of-flow under multicol Bug: 1076503 Change-Id: I2ebfa1eb7926cf760ff7ffbe9b4c3a98997339dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2186741 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#766419} -- wpt-commits: d84a7b39d39499252ba9bf743a5a0f198b500565 wpt-pr: 23450
4acb34771181a80169b5b0cc3c77bcdafcd53e9b: Bug 1636126 [wpt PR 23460] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 07 May 2020 17:10:59 +0000 - rev 594881
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636126 [wpt PR 23460] - Update wpt metadata, a=testonly wpt-pr: 23460 wpt-type: metadata
1b8d9b42030b6838680f13670b5e3cf89aebcc88: Bug 1636126 [wpt PR 23460] - Improve test: csp/reporting/post-redirect-stacktrace.https.html, a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Wed, 13 May 2020 09:46:08 +0000 - rev 594880
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636126 [wpt PR 23460] - Improve test: csp/reporting/post-redirect-stacktrace.https.html, a=testonly Automatic update from web-platform-tests Improve test: csp/reporting/post-redirect-stacktrace.https.html The test was checking no post-redirect information was leaked. Unfortunately, there was a bug in the test. The same data was present in both the final URL and the post-redirect URL. This patch make the post-redirect URL no to have the data. BUG=1074317 Change-Id: I40a698b8edf6ff651dda5d0e82b803a60ccaac7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2187711 Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#766412} -- wpt-commits: 48bd16d814c723f06e1a5bcc7cf469b7d8360157 wpt-pr: 23460
57955425cef9cf56d74985beec78d02b75dec371: Bug 1635988 [wpt PR 23444] - [css-pseudo] Fix legacy ::marker originated by pseudo-element multicol, a=testonly
Oriol Brufau <obrufau@igalia.com> - Wed, 13 May 2020 09:46:01 +0000 - rev 594879
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635988 [wpt PR 23444] - [css-pseudo] Fix legacy ::marker originated by pseudo-element multicol, a=testonly Automatic update from web-platform-tests [css-pseudo] Fix legacy ::marker originated by pseudo-element multicol This patch fixes a heap-use-after-free in legacy layout when having a an inside ::marker originated by a ::before or ::after pseudo-element which is dynamically converted into a multicol container. The problem was caused by some code that was aiming to prevent the ::marker from being placed after the generated contents of the ::before or ::after. To do so, it reinserted the ::marker as the first child of the originating list item. The problem was that, in the multicol case, the LayoutInsideListMarker is a descendant (not a child) of the LayoutListItem, since there are a LayoutMultiColumnFlowThread and a LayoutBlockFlow between them. Therefore, this patch reinserts the ::marker as the first child of its parent, instead of as the first child of the list item. BUG=1078236 TEST=third_party/blink/web_tests/external/wpt/css/css-multicol/multicol-list-item-002.html Change-Id: I580e4730d6e8ec6d41e423d0d027f67de4d48fa5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2185030 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#766374} -- wpt-commits: e2ccd98281015fdf8eae6ac91a8a0ce556e07c73 wpt-pr: 23444
6c00c7d27f0b01d6f7830d5f0d01693ccd071185: Bug 1636066 [wpt PR 23452] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 07 May 2020 12:51:06 +0000 - rev 594878
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636066 [wpt PR 23452] - Update wpt metadata, a=testonly wpt-pr: 23452 wpt-type: metadata
db5e4f264153f9968c7c97298cdc8e316586000e: Bug 1636066 [wpt PR 23452] - Adjust font-size expectation for none/mprescripts, a=testonly
Rob Buis <rbuis@igalia.com> - Wed, 13 May 2020 09:45:53 +0000 - rev 594877
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636066 [wpt PR 23452] - Adjust font-size expectation for none/mprescripts, a=testonly Automatic update from web-platform-tests Skip font-size subtest for none/mprescripts (#23452) The none and mprescripts test fragments are represented using mmultiscripts and subject to a CSS rule that increases the scriptlevel, causing the computed font-size to be a fraction string and hard to test accurately between implementations, so skip it for now. -- wpt-commits: 585eeec5f5f2c5055c70a48593a7adbd4b8a34eb wpt-pr: 23452
56b03c5d981273f70e61294027c763cbac6a351c: Bug 1589335 [wpt PR 19754] - Let retry.py flush stdout after each log message, a=testonly
Philip Jägenstedt <philip@foolip.org> - Wed, 13 May 2020 09:45:48 +0000 - rev 594876
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1589335 [wpt PR 19754] - Let retry.py flush stdout after each log message, a=testonly Automatic update from web-platform-tests Let retry.py flush stdout after each log message (#19754) This is to avoid the subprocess output appearing before the "Running %s [try %d/%d]" message. -- wpt-commits: ca16f38e880d60c9721566251597cc9aae1f9778 wpt-pr: 19754
8db0cdde1d281d407b6df3f94b715417e2d76480: Bug 1636045 [wpt PR 23420] - Fix "auto" outline with padding and overflowing inline descendants, a=testonly
Manuel Rego Casasnovas <rego@igalia.com> - Wed, 13 May 2020 09:45:43 +0000 - rev 594875
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636045 [wpt PR 23420] - Fix "auto" outline with padding and overflowing inline descendants, a=testonly Automatic update from web-platform-tests Fix "auto" outline with padding and overflowing inline descendants This patch fixes a regression in LayoutNG compared to legacy, when the descendant of an element with padding and "outline: auto" is an inline block. And also when it's an inline element (which was not working properly in legacy layout either, that's why outline-025 and outline-026 tests fail on legacy). We need to rebaseline an old pixel test, as we're coming back to the legacy layout behavior for it. BUG=1078539 TEST=external/wpt/css/css-ui/outline-024.html TEST=external/wpt/css/css-ui/outline-025.html TEST=external/wpt/css/css-ui/outline-026.html Change-Id: I8ccf72fb34e1d9ce6821eec9312f1fecd52e1281 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182471 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#766312} -- wpt-commits: 663e39d65620ff336e5183b0b4c2a7bb1636c2c7 wpt-pr: 23420
bbff8a3ac01236bd57bde28f8f842e81e8e2cc48: Bug 1635195 [wpt PR 23387] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 07 May 2020 08:38:44 +0000 - rev 594874
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635195 [wpt PR 23387] - Update wpt metadata, a=testonly wpt-pr: 23387 wpt-type: metadata
32a8bc27a071addb08078a33705e5aaa91538955: Bug 1635195 [wpt PR 23387] - Let 'revert' keyword restore native appearance, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Wed, 13 May 2020 09:45:35 +0000 - rev 594873
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635195 [wpt PR 23387] - Let 'revert' keyword restore native appearance, a=testonly Automatic update from web-platform-tests Let 'revert' keyword restore native appearance Recently, we changed our behavior w.r.t. auto-disabling of native appearance on UI elements: we now disable the appearance if any author declaration is seen for background/border, even if those declarations match the UA-specified style. Technically, an author-level 'revert' is still an author declaration, so blindly following the above rules would still disable the native appearance. However, it would not match the author expectation for 'revert'. It is natural that e.g. 'all:revert' on UI elements restore exactly the style the element would have had without author styles. This CL adds kBorder/kBackground flags, and a mechanism for collecting all CSSProperty::Flags seen for the kAuthor origin. Those flags are then used at the end of the Apply process to provide values for SetHasAuthorBorder/Background. Also fix test with commented out subtests, and add bonus test for css-logical. Bug: 579788, 1061846 Change-Id: Ie88d666597f6aa8b38657d9c20fe3006ed5a8e39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2178891 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#766307} -- wpt-commits: 15d5f975f5ee447a470e1cb69a678202cffe7406 wpt-pr: 23387
2caad7825718d42aed047e4e568b97f1873877b0: Bug 1475158 [wpt PR 11935] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 11 May 2020 20:27:40 +0000 - rev 594872
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1475158 [wpt PR 11935] - Update wpt metadata, a=testonly wpt-pr: 11935 wpt-type: metadata
9d93ae046a716cef3d258e4ec6f78148f49833e0: Bug 1475158 [wpt PR 11935] - [webaudio] Generalize convolver test tolerances for numerical error, a=testonly
Karl Tomlinson <orders+github@karlt.net> - Wed, 13 May 2020 09:45:18 +0000 - rev 594871
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1475158 [wpt PR 11935] - [webaudio] Generalize convolver test tolerances for numerical error, a=testonly Automatic update from web-platform-tests [webaudio] Generalize convolver test tolerances for numerical error (#11935) * [webaudio] Generalize convolver test tolerances for numerical error Gecko uses FFTs for convolution, even with short response buffers, and so precision would be expected to be similar to that with longer buffers in Blink and Webkit. In Gecko, the actual calculations performed depend on what instructions are available on the processor, and different code is used on some platforms. The precision in the answers is similar with different processors and code, but the slightly larger errors may occur in different tests. This patch picks a single expected precision for similar tests and uses that for all such tests. -- wpt-commits: 366ea5235785a583a1079821cb88d735d3835aec wpt-pr: 11935
2683fb6ee8b7153cdd264e60d944231d35110059: Bug 1636017 [wpt PR 23449] - css-ruby: Fix incorrect tests in ruby-position.html, a=testonly
Kent Tamura <tkent@chromium.org> - Wed, 13 May 2020 09:45:13 +0000 - rev 594870
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1636017 [wpt PR 23449] - css-ruby: Fix incorrect tests in ruby-position.html, a=testonly Automatic update from web-platform-tests css-ruby: Fix incorrect tests in ruby-position.html ruby-position property should work with 'ruby text container boxes'. So ruby-position on <rt> should not work. https://drafts.csswg.org/css-ruby-1/#rubypos Bug: https://github.com/web-platform-tests/wpt/issues/23386 Change-Id: I3c3e7a762c8f88d5ffce1101692b06b6e496e49d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2186615 Commit-Queue: Koji Ishii <kojii@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#766290} -- wpt-commits: bf9b762dad89dd35757cd160fc9d96c385a873b6 wpt-pr: 23449
58cad4098789d440e85da22295bbb7b9a7404422: Bug 1635804 [wpt PR 23432] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 07 May 2020 04:37:05 +0000 - rev 594869
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635804 [wpt PR 23432] - Update wpt metadata, a=testonly wpt-pr: 23432 wpt-type: metadata
e89c41f66d9a14e80b231a13a3fc2a58e9e7a47f: Bug 1635804 [wpt PR 23432] - URL: test IDNA ignored code points in host, a=testonly
Rimas Misevičius <rmisev3@gmail.com> - Wed, 13 May 2020 09:45:05 +0000 - rev 594868
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635804 [wpt PR 23432] - URL: test IDNA ignored code points in host, a=testonly Automatic update from web-platform-tests URL: test IDNA ignored code points in host See https://github.com/whatwg/url/pull/497 for context. -- wpt-commits: e9a106175a02a192a7239f42a94235fbe0f0c7a3 wpt-pr: 23432
fb8445a47c0f806c50ed6c4ffb67c178ff945858: Bug 1635994 [wpt PR 23445] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 07 May 2020 01:37:42 +0000 - rev 594867
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635994 [wpt PR 23445] - Update wpt metadata, a=testonly wpt-pr: 23445 wpt-type: metadata
02bfd75f08d156e72353067504fa700dbab638cc: Bug 1635994 [wpt PR 23445] - [css-flexbox-1][css-overflow-3] Add tests for capturing margin/padding in flex overflow., a=testonly
fantasai <fantasai.bugs@inkedblade.net> - Wed, 13 May 2020 09:44:56 +0000 - rev 594866
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635994 [wpt PR 23445] - [css-flexbox-1][css-overflow-3] Add tests for capturing margin/padding in flex overflow., a=testonly Automatic update from web-platform-tests [css-flexbox-1][css-overflow-3] Add tests for capturing margin/padding in flex overflow. -- wpt-commits: 899d979003ae8e678d4a45ec5334451e75e4b367 wpt-pr: 23445
f39c26c827372b3c990b57a768709affbd8c8174: Bug 1635896 [wpt PR 23440] - Update interfaces/webrtc-stats.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 13 May 2020 09:44:51 +0000 - rev 594865
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635896 [wpt PR 23440] - Update interfaces/webrtc-stats.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webrtc-stats.idl (#23440) Source: https://github.com/tidoust/reffy-reports/blob/a0869ef/ed/idl/webrtc-stats.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/683960541 -- wpt-commits: ba6082e94163d5f024974ec6e4a65c95ce690829 wpt-pr: 23440
e750ec743e29f7f14bcc406317cd73d283eb995f: Bug 1635971 [wpt PR 23443] - [idle] Change threshold option from seconds to milliseconds, a=testonly
Reilly Grant <reillyg@chromium.org> - Wed, 13 May 2020 09:44:46 +0000 - rev 594864
Push 13186 by ffxbld-merge at Mon, 01 Jun 2020 09:52:46 +0000
Bug 1635971 [wpt PR 23443] - [idle] Change threshold option from seconds to milliseconds, a=testonly Automatic update from web-platform-tests [idle] Change threshold option from seconds to milliseconds According to the W3C TAG design principles[1] any web API that accepts a time measurement should do so in milliseconds, even if seconds is more natural. In the process of testing this I noticed that this option should be declared with [EnforceRange] as otherwise the V8 bindings will interpret negative values as large positive values. Spec PR: https://github.com/samuelgoto/idle-detection/pull/17 [1]: https://w3ctag.github.io/design-principles/#milliseconds Bug: 878979 Change-Id: Ib0e0c3567c5e0efdf283d5024598da8997e8e93c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181910 Commit-Queue: Reilly Grant <reillyg@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Cr-Commit-Position: refs/heads/master@{#765639} -- wpt-commits: d567a81805f4614a0a4d295bee11e9fee99aa219 wpt-pr: 23443
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip