d1d850a707b8ad427a3d1069d29ceb64a74ae4df: Bug 1534487 [wpt PR 15734] - Revert "[Animation Worklet] Remove unnecessary force composition", a=testonly
Yi Gu <yigu@chromium.org> - Tue, 26 Mar 2019 14:04:31 +0000 - rev 467275
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534487 [wpt PR 15734] - Revert "[Animation Worklet] Remove unnecessary force composition", a=testonly Automatic update from web-platform-tests Revert "[Animation Worklet] Remove unnecessary force composition" This reverts commit b9fdefc5712d3ec3b2482ad9c2af1c2e6fa6b25a. Reason for revert: Removing compositing caused flaky on Mac Original change's description: > [Animation Worklet] Remove unnecessary force composition > > We used to have will-change: transform in test reference but they are > no longer needed. > > Change-Id: Ib6870863760e32de201a0560fa59f43634c72da8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1504711 > Commit-Queue: Yi Gu <yigu@chromium.org> > Reviewed-by: Xida Chen <xidachen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#638107} TBR=xidachen@chromium.org,yigu@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: I1350b6c5e53e35fd0fb5de035e33c9f44528a4c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1510077 Reviewed-by: Yi Gu <yigu@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#638867} -- wpt-commits: 4371a004caa7771794a31109bc019e001799f8e2 wpt-pr: 15734
41225572b484b9c05344383b094a40b96c41337d: Bug 1534192 [wpt PR 15719] - Change each sleep to be shorter when waiting for servers to come up, a=testonly
Sam Sneddon <me@gsnedders.com> - Tue, 26 Mar 2019 14:04:28 +0000 - rev 467274
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534192 [wpt PR 15719] - Change each sleep to be shorter when waiting for servers to come up, a=testonly Automatic update from web-platform-tests Change each sleep to be shorter when waiting for servers to come up (#15719) -- wpt-commits: 8a14626934f5748a4ea6210847a02c0d8bbc8560 wpt-pr: 15719
4c7ce8c319e974f19c25f9f802cfdd40b205dfa6: Bug 1534353 [wpt PR 15504] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 12 Mar 2019 00:59:35 +0000 - rev 467273
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534353 [wpt PR 15504] - Update wpt metadata, a=testonly wpt-pr: 15504 wpt-type: metadata
374a0fc6fe9d457d7c99a635b3cf0ce70eb5b284: Bug 1534353 [wpt PR 15504] - Add tests for stale while revalidate handling with service workers., a=testonly
Dave Tapuska <dtapuska@chromium.org> - Tue, 26 Mar 2019 13:55:40 +0000 - rev 467272
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534353 [wpt PR 15504] - Add tests for stale while revalidate handling with service workers., a=testonly Automatic update from web-platform-tests Add tests for stale while revalidate handling with service workers. Chrome currently fails these tests and it will be enabled in a followup patch. The intent of this change is to add the wpt tests and bring the code closer to the proposed specification. BUG=348877 Change-Id: Ie9894c588b2cfe040be97905617b05c5b49fc4f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1479576 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#638586} -- wpt-commits: 7e2bcbc6ae0ab383f02cb4c10a9e8091c30ef61c wpt-pr: 15504
d783e54adf7f92dab060c7e5f5f7f26317f7ee82: Bug 1534111 [wpt PR 15703] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 12 Mar 2019 00:54:09 +0000 - rev 467271
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534111 [wpt PR 15703] - Update wpt metadata, a=testonly wpt-pr: 15703 wpt-type: metadata
f6ac89e9c244750e101ba07eb75ba4c5fa23b125: Bug 1534111 [wpt PR 15703] - CacheStorage: Set the Response mime type based on stored content-header., a=testonly
Ben Kelly <wanderview@chromium.org> - Tue, 26 Mar 2019 13:55:34 +0000 - rev 467270
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534111 [wpt PR 15703] - CacheStorage: Set the Response mime type based on stored content-header., a=testonly Automatic update from web-platform-tests CacheStorage: Set the Response mime type based on stored content-header. Previously the Response mime type was never set when reading from a Cache. This resulted in empty string blob.type values and could also prevent code cache from being generated if a script Response was put back into a Cache. This CL makes us at least generate a mime type from the current content-type header. This is a partial solution since the mime type should technically be frozen at initial Response construction time even if the content-type header is later changed. To support that we will need to explicitly store a mime type on disk in the cache. This will be done later in crbug.com/938939. Bug: 937963,938939 Change-Id: Iabfe3909ff35957501ef33132af2a0c1f70c5c94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506213 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#638581} -- wpt-commits: 1e60ccdb7a01f6763c7e29909264dff64bdb4265 wpt-pr: 15703
875a1979d02963e8d2188cf2a42edf34fd923f05: Bug 1534122 [wpt PR 15706] - Isolation: Remove isolation if we have non-svg replaced content., a=testonly
Vladimir Levin <vmpstr@chromium.org> - Tue, 26 Mar 2019 13:55:32 +0000 - rev 467269
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534122 [wpt PR 15706] - Isolation: Remove isolation if we have non-svg replaced content., a=testonly Automatic update from web-platform-tests Isolation: Remove isolation if we have non-svg replaced content. This patch ensures that we don't put isolation nodes in place if we have replaced content transform in an non-svg. The reason for this is twofold: 1. Typically, isolation wouldn't buy us anything, since we're likely looking at an image, which has no subtree to isolate. 2. When we get the chain of transforms, we need to decide whether we're returning a replaced content or an isolation transform since they are both leafs of a chain, but not a part of the same chain. Currently we return the isolation node first. We could fix this by returning the replaced content first, but then we specifically bypass transform isolation which may cause other bugs down the line. R=pdr@chromium.org Bug: 937571 Change-Id: I39f51a2e7810f058bfdf49c28c8f2e3857565ebe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506572 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#638271} -- wpt-commits: 1566432e3f28635f31bf618c56698724d58beead wpt-pr: 15706
18fb7bd95d12a7f535be2fda194e4b5cab9620db: Bug 1478472 [wpt PR 12187] - Add support for fuzzy matching in reftests., a=testonly
jgraham <james@hoppipolla.co.uk> - Tue, 26 Mar 2019 13:55:29 +0000 - rev 467268
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1478472 [wpt PR 12187] - Add support for fuzzy matching in reftests., a=testonly Automatic update from web-platform-tests Add support for fuzzy matching in reftests (#12187) This allows fuzzy matching in reftests in which a comparison can succeed if the images are different within a specified tolerance. It is useful in the case of antialiasing, and in other scenarios where it's not possible to make an exact match in all cases. Differences between tests are characterised by two values: * The maximum difference for any pixel on any color channel (in the range 0 to 255) * The maximum total number of differing pixels The fuzziness can be supplied in two places, according to whether it's a property of the test or of the implementation: * In the reftest itself, using a <meta name=fuzzy> tag * In the expectation metadata file using a fuzzy: key that takes a list The general format of the fuzziness specifier is range = [name "="] [digits, "-"], digits fuzziness = [ url, "-" ], range, ";", range name = "maxDifference" | "totalPixels" The first range represents the maximum difference of any channel per pixel and the second represents the total number of pixel differences. So for example a specifier could be: * "maxDifference=10;totalPixels=300" - meaning a difference of exactly 10 per color channel and exactly 300 pixels different in total (all ranges are inclusive). * "5-10;200-300" - meaning a maximum difference of between 5 and 10 per color channel and between 200 and 300 pixels differing in total The definition of url is a little different between the meta element and the expecation metadata. In the first case the url is resolved against the current file, and applies to any reference in the current file with that name. So for example <meta name="fuzzy" content="option-1-ref.html:5;200"> would allow a fuzziness of up to 5 on a specific channel and up to 200 opixels different for comparisons involving the file containing the meta element and option-1-ref.html. In the case of expectation metadata, the metadata is always associated with the root test, so urls are always resolved relative to that. In the case as above where only a single URL is supplied, any reference document with that URL will have the fuzziness applied for whatever comparisons it's involved in e.g. [test1.html] fuzzy: option-1-ref.html:5;200 would apply the fuziness to any comparison involving option-1-ref.html whilst running the set of reftests rooted on test1.html. To specify an exact comparison for the fuzziness, one can also supply a full reference pair e.g. [test1.html] fuzzy: subtest.html==option-1-ref.html:5;200 in which case the fuzziness would only apply to "match" comparison involving subtest.html on the lhs and option-1-ref.html on the rhs (both resolved relative to test1.html). -- wpt-commits: 1f570a686843ca10f151a79956ee16110f4a4d42 wpt-pr: 12187
88d4845c21396701d526fd9b1303fe715b3e065f: Bug 1531625 [wpt PR 15561] - HTML: window.closed, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 26 Mar 2019 13:55:27 +0000 - rev 467267
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1531625 [wpt PR 15561] - HTML: window.closed, a=testonly Automatic update from web-platform-tests HTML: window.closed For https://github.com/whatwg/html/pull/4402. -- wpt-commits: 391ee6b42d91d930f73825912b32928ea32f004c wpt-pr: 15561
4895b4270c4535846b0856f90143950fa0306c52: Bug 1534191 [wpt PR 15718] - Don't stop text-decoration propagation at non-UA shadow boundaries., a=testonly
Rune Lillesveen <futhark@chromium.org> - Tue, 26 Mar 2019 13:55:25 +0000 - rev 467266
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534191 [wpt PR 15718] - Don't stop text-decoration propagation at non-UA shadow boundaries., a=testonly Automatic update from web-platform-tests Don't stop text-decoration propagation at non-UA shadow boundaries. There is no spec saying this should happen. Neither Gecko nor WebKit does this, and it breaks devtools UX. We still need to stop propagation into UA shadow trees to avoid text-decoration applying to media controls, for instance. Bug: 938193 Change-Id: I21895cb36b0d0bf2b39b42c000d3cf5ceb4255f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508097 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Hayato Ito <hayato@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#638571} -- wpt-commits: a9dee916c907b7749a611848308708e9890dbfac wpt-pr: 15718
9fc64710bd7382aff99037effa01f444c40c1989: Bug 1533476 [wpt PR 15659] - Fix #15625: deal with Safari throwing when moving the window to (0,0), a=testonly
Sam Sneddon <me@gsnedders.com> - Tue, 26 Mar 2019 13:55:23 +0000 - rev 467265
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1533476 [wpt PR 15659] - Fix #15625: deal with Safari throwing when moving the window to (0,0), a=testonly Automatic update from web-platform-tests Fix #15625: deal with Safari throwing when moving the window to (0,0) (#15659) This is fixed in STP and likely will not persist beyond Safari 12. -- wpt-commits: d1ef68162b8118fec533199c19f75aa27240318d wpt-pr: 15659
f7168b12c0c3b99e3dcbc81143b397a7f1c054d9: Bug 1533964 [wpt PR 15683] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 12 Mar 2019 00:13:19 +0000 - rev 467264
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1533964 [wpt PR 15683] - Update wpt metadata, a=testonly wpt-pr: 15683 wpt-type: metadata
a82915af92b900df297b6f767d9e63da546883aa: Bug 1533964 [wpt PR 15683] - Improve tainting for filter primitives, a=testonly
Fredrik Söderquist <fs@opera.com> - Tue, 26 Mar 2019 13:55:17 +0000 - rev 467263
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1533964 [wpt PR 15683] - Improve tainting for filter primitives, a=testonly Automatic update from web-platform-tests Improve tainting for filter primitives This makes tainting for many filter primitives less pessimistic, by implementing the "Tainted Filter Primitives" section [1] from the specification. For feFlood/feDropShadow: A value of 'currentcolor' for 'flood-color' taints. For feSpecularLighting/feDiffuseLighting: A value of 'currentcolor' for 'lighting-color' taints. For the other primitives (which currently lack any specific logic), i.e: feBlend, feComponentTransfer, feComposite, feConvolveMatrix, feDisplacementMap, feGaussianBlur, feMorphology, feOffset and feTile no local tainting is performed (the TaintsOrigin() override is returning false). The signature/convention of the TaintsOrigin() is changed by removing the |inputs_taint_origin| argument, and always taint the primitive if it (the flag returned by FilterEffect::InputsTaintOrigin) is true. This saves each primitive to have to relate to this flag. (For primitives that have no inputs this flag would always be false regardless.) This means that TaintsOrigin() for each primitive is now essentially computing the "local" tainting state. [1] https://drafts.fxtf.org/filter-effects/#tainted-filter-primitives Bug: 792518 Change-Id: Ie2d45eeb1ae8478009b88b8b87b3c4c325ede306 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503257 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#638546} -- wpt-commits: 41a36beff1e1145e756f4c1d505ff7c67785f2af wpt-pr: 15683
f9cae313fbd8b503eb80f4cc4563eb2a82928f0c: Bug 1529188 [wpt PR 15468] - [Import Maps] implement "Packages" via trailing slashes, a=testonly
Hiroshige Hayashizaki <hiroshige@chromium.org> - Tue, 26 Mar 2019 13:55:00 +0000 - rev 467262
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1529188 [wpt PR 15468] - [Import Maps] implement "Packages" via trailing slashes, a=testonly Automatic update from web-platform-tests [Import Maps] implement "Packages" via trailing slashes This CL also implements "most-specific wins" rule. https://github.com/WICG/import-maps/issues/102 Bug: 928149 Change-Id: I484266086bbe244de8b43ceeddacc8552307b7f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1475049 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#638532} -- wpt-commits: f55313aae84eb0d2d42d1c1356732eda0540fc3f wpt-pr: 15468
8e9451e6fe56e265ef1901ca459581ab86df1a01: Bug 1534141 [wpt PR 15709] - Make updater code exclude meaningless manifest item types., a=testonly
Josh Matthews <josh@joshmatthews.net> - Tue, 26 Mar 2019 13:54:58 +0000 - rev 467261
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534141 [wpt PR 15709] - Make updater code exclude meaningless manifest item types., a=testonly Automatic update from web-platform-tests Exclude reftest_base types from the test tree. -- Remove RefTestBase from the known item mappings. -- wpt-commits: 4f64577312174deca261f5642c896ce33117fbf8, 405751fab6fec48b30c28bfa0f6b86fe056ee425 wpt-pr: 15709
a1d3d4305894c75f7c9995028c1a667c8f9e23cf: Bug 1533859 [wpt PR 15677] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 14 Mar 2019 07:37:47 +0000 - rev 467260
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1533859 [wpt PR 15677] - Update wpt metadata, a=testonly wpt-pr: 15677 wpt-type: metadata
3833d15e01d1f932b4602917cab0706dcc0d1bf1: Bug 1533859 [wpt PR 15677] - Fix Acid2 to take the screenshot after it loads, a=testonly
Sam Sneddon <me@gsnedders.com> - Tue, 26 Mar 2019 13:54:52 +0000 - rev 467259
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1533859 [wpt PR 15677] - Fix Acid2 to take the screenshot after it loads, a=testonly Automatic update from web-platform-tests Fix Acid2 to take the screenshot after loading & scrolling -- Add a reference for Acid2 that should pixel-for-pixel match Per https://bugzilla.mozilla.org/show_bug.cgi?id=343583#c6, Hixie never intended the reference.png to match exactly (e.g., the nose especially is quite fragile with anti-aliasing differences). This is based on the test itself, but by and large just uses block layout with pretty simple border/backgrounds. The only complexity is in the eyes (where layering is needed to get the background interpolated as on the test) and the nose (which mostly matches the test as browsers trivially differ around the aliasing of border edges). -- wpt-commits: 8a28e1a47287265e54f3c28650f3201f6f3e7dff, 42330b2ea1aa9e8c23fb2fbcfcba9f8cabd9bb18 wpt-pr: 15677
1bcfaece589b4d76a626f7820f785e225ea9045d: Bug 1532151 [wpt PR 15520] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 06 Mar 2019 17:26:08 +0000 - rev 467258
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1532151 [wpt PR 15520] - Update wpt metadata, a=testonly wpt-pr: 15520 wpt-type: metadata
9c7c08557a12121cd1144f02ad10ee231b267d00: Bug 1532151 [wpt PR 15520] - Add support for AudioContextOptions sampleRate, a=testonly
Andrew MacPherson <andrew.macpherson@soundtrap.com> - Tue, 26 Mar 2019 13:54:45 +0000 - rev 467257
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1532151 [wpt PR 15520] - Add support for AudioContextOptions sampleRate, a=testonly Automatic update from web-platform-tests Add support for AudioContextOptions sampleRate Optional sampleRate parameter to AudioContextOptions, if provided then the AudioContext will run at this sampleRate, otherwise it will run at the hardware rate. Running the AudioContext at a lower sample rate can allow running a heavier graph on low-end devices, for example if a given device is able to run with X nodes at a sample rate of 48k, it can support roughly 2X nodes at 24k or 4X nodes at 12k. Bug: 432248 Change-Id: I835f28b4625763bd6a6ddbee9b89636ef8a8a066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1482957 Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Andrew MacPherson <andrew.macpherson@soundtrap.com> Cr-Commit-Position: refs/heads/master@{#638498} -- wpt-commits: 9b994b36003246370b352fa70c563866a8443e4e wpt-pr: 15520
c1ae8fa14e174cd51576e4b63a69d88e1180c64a: Bug 1534176 [wpt PR 15518] - HTML: opener and discarded auxiliary browsing context, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 26 Mar 2019 13:54:41 +0000 - rev 467256
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534176 [wpt PR 15518] - HTML: opener and discarded auxiliary browsing context, a=testonly Automatic update from web-platform-tests HTML: opener and discarded auxiliary browsing context For https://github.com/whatwg/html/pull/4379. -- wpt-commits: 3df07160e80e074edf0579627b7d5689f7bebf7b wpt-pr: 15518
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip