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 531124
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531123
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531122
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531121
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531120
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531119
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531118
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531117
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531116
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531115
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531114
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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 531113
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +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
d26a6402ab4fc7e447bb20dafe28a761934b398d: Bug 1635957 [wpt PR 23418] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 06 May 2020 23:09:44 +0000 - rev 531112
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1635957 [wpt PR 23418] - Update wpt metadata, a=testonly wpt-pr: 23418 wpt-type: metadata
4c27e5fdfd1df86d8d593fe0535e8652d92986a0: Bug 1635957 [wpt PR 23418] - Use the backdrop filter's clip for synthetic effects and layers, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Wed, 13 May 2020 09:44:38 +0000 - rev 531111
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1635957 [wpt PR 23418] - Use the backdrop filter's clip for synthetic effects and layers, a=testonly Automatic update from web-platform-tests Use the backdrop filter's clip for synthetic effects and layers Previously for a synthetic effect and the associated synthesized mask layer, we used the clip that introduce the synthetic effect as their clip state, causing incorrect clipping of backdrop filters. Now use the clip of the backdrop filter for synthetic effects and layers to avoid the problem. ClipPaintPropertyNode rounded_clip ClipPaintPropertyNode rect_clip EffectPaintPropertyNode backdrop_filter clip=rect_clip The cc effect tree is like mask_isolation (backdrop filter moved here) / \ mask_effect node_for_backdrop_filter When we create the cc node for backdrop_filter, we find that there is an ancestor clip (rounded_clip) needs a synthetic effect and synthesized mask, so create mask_isolation and mask_effect nodes and a mask clip layer. To let the backdrop filter access the correct backdrop, we move the backdrop filter up to mask_isolation, requiring that mask_isolation to use the backdrop_filter's clip (rect_clip) instead of the clip (rounded_clip) that introduces the synthetic effect, to ensure the backdrop filter is correctly clipped. This in turn requires that mask_effect and the mask layer also use rect_clip as their clip state to ensure proper clip hierarchy. Bug: 1077137 Change-Id: Ib9c3cc7e8db5b1b261b3a758f2fb6680e0f5ab1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2183198 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#766158} -- wpt-commits: 4b3fd166980ee106af2db6ca6a8c653fb07a517c wpt-pr: 23418
ca2477055eba8090b89d3fbeed429643b882f589: Bug 1626529 [wpt PR 22594] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 06 May 2020 22:50:59 +0000 - rev 531110
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1626529 [wpt PR 22594] - Update wpt metadata, a=testonly wpt-pr: 22594 wpt-type: metadata
9f3527240d8041d1b6ae5acbdf4f92f5a740d158: Bug 1626529 [wpt PR 22594] - Fix broken link, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Wed, 13 May 2020 09:44:22 +0000 - rev 531109
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1626529 [wpt PR 22594] - Fix broken link, a=testonly Automatic update from web-platform-tests Fix borken link (#22594) -- wpt-commits: a794d31daf67a801d59a38a35674deeb61034a4f wpt-pr: 22594
d318fb86b3225bc87c4faee9c4c0f7fcc0eafd5e: Bug 1633611 [wpt PR 23285] - Idle: Add notification permission check, a=testonly
Ayu Ishii <ayui@chromium.org> - Wed, 13 May 2020 09:44:16 +0000 - rev 531108
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1633611 [wpt PR 23285] - Idle: Add notification permission check, a=testonly Automatic update from web-platform-tests Idle: Add notification permission check This change checks for notification permission before allowing idle detection. tested locally / wpt / unittest Bug: 1074049 Change-Id: I5d12efaf5cb68020ed10eccf577d38319592f4f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163638 Commit-Queue: Ayu Ishii <ayui@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#764754} -- wpt-commits: 6d1a21bee19885b49dddb5cd234beea4e162b306 wpt-pr: 23285
877e73caedb35f2dca41703f3fb84eac82cec06d: Bug 1635673 [wpt PR 23412] - [ResourceTiming] Dispatch entry for 404 scripts, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Wed, 13 May 2020 09:44:08 +0000 - rev 531107
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1635673 [wpt PR 23412] - [ResourceTiming] Dispatch entry for 404 scripts, a=testonly Automatic update from web-platform-tests [ResourceTiming] Dispatch entry for 404 scripts This CL fixes dispatching PerformanceResourceTiming entries when the resource was a 404 script. These do not go through HandleLoaderFinish() and instead go through HandleLoaderError(). The ResourceTimingInfo was already being discarded in that method, so instead we report the entry as resources with error statuses must be reported. Bug: 883400 Change-Id: I72e95b79f70f10b3f1f9c18a8053d2a31f5a6008 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181828 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#766123} -- wpt-commits: f4bf034f4fd62cfebc956b9d1a0b8fd48398674c wpt-pr: 23412
e8c21c7b788b39f6149d47352ece2bb9c0cde7b5: Bug 1635845 [wpt PR 23430] - Mark web-animations/idlharness.window.html as timeout=long, a=testonly
Yi Gu <yigu@chromium.org> - Wed, 13 May 2020 09:44:03 +0000 - rev 531106
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1635845 [wpt PR 23430] - Mark web-animations/idlharness.window.html as timeout=long, a=testonly Automatic update from web-platform-tests Mark web-animations/idlharness.window.html as timeout=long It's symptomatic of crbug.com/1047818. Similar to crrev.com/c/2177456, mark the test timeout=long. Bug: 1078682 Change-Id: Ibb803e34d1626659bccbfdb6deb7074a70acea44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2184058 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#766027} -- wpt-commits: bbf2121805c1ddcfb559a4f619be58f1bd46b938 wpt-pr: 23430
06b3f3c7ce4b85fcc211bbddc0887dd08963122d: Bug 1635780 [wpt PR 23427] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 06 May 2020 18:29:06 +0000 - rev 531105
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1635780 [wpt PR 23427] - Update wpt metadata, a=testonly wpt-pr: 23427 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip