b6356833b51395d89751d8cb9748e5dcb72dc955: Bug 1534496 [wpt PR 15747] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 15 Mar 2019 20:17:46 +0000 - rev 467284
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534496 [wpt PR 15747] - Update wpt metadata, a=testonly wpt-pr: 15747 wpt-type: metadata
0f50239333881a1f02940175cbfa37dc17bab57a: Bug 1534496 [wpt PR 15747] - Fixed flaky playback-rate test., a=testonly
Olga Gerchikov <gerchiko@microsoft.com> - Tue, 26 Mar 2019 14:05:17 +0000 - rev 467283
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534496 [wpt PR 15747] - Fixed flaky playback-rate test., a=testonly Automatic update from web-platform-tests Fixed flaky playback-rate test. Root cause for the flakiness: 1.Due to crbug.com/937382, composited worklet animation current time is not identical to the current time passed to the animator instance in the worklet scope (which is passed through to local time in this test). 2.Not waiting enough for the compositing thread to update the styles. The fix: 1.Changed the test to compare against reference worklet animation's effect local time that has default playback rate. 2.Explicitly wait for the style updates before comparing to the expected results. Bug: 915352 Change-Id: I35cb3f89048568bc830aff8a6473f6d2aef5aaeb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497789 Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#638721} -- wpt-commits: 02aa554ae40ec5eef25f945420a4cb7368054d2d wpt-pr: 15747
6b643c6609e13226b3e4dec56abc9f7a8f3cc362: Bug 1534493 [wpt PR 15649] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 15 Mar 2019 20:00:08 +0000 - rev 467282
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534493 [wpt PR 15649] - Update wpt metadata, a=testonly wpt-pr: 15649 wpt-type: metadata
8ab89f51fe694e4f03177084635f89b7512c9bbb: Bug 1534493 [wpt PR 15649] - HTML: test queueing behavior of window.close(), a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 26 Mar 2019 14:05:12 +0000 - rev 467281
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534493 [wpt PR 15649] - HTML: test queueing behavior of window.close(), a=testonly Automatic update from web-platform-tests HTML: test queueing behavior of window.close() For https://github.com/whatwg/html/pull/4402. -- wpt-commits: bdb6041d03facf7c79c9df62659c6bd0fb2adfc3 wpt-pr: 15649
8c6864d28e68febc3a6cf982105407f9573293cd: Bug 1527376 [wpt PR 15336] - Implemented setPlaybackRate for scroll-linked Worklet Animations., a=testonly
Olga Gerchikov <gerchiko@microsoft.com> - Tue, 26 Mar 2019 14:04:54 +0000 - rev 467280
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1527376 [wpt PR 15336] - Implemented setPlaybackRate for scroll-linked Worklet Animations., a=testonly Automatic update from web-platform-tests Implemented setPlaybackRate for scroll-linked Worklet Animations. • Updated logic of calculating initial current time of non-composited scroll-linked animations to ensure that the start time is always initialized to zero. • Changed signature of cc::ScrollTimeline::CurrentTime to return base::Optional<base::TimeTicks>. This is to enforce cc: WorkletAnimation::CurrentTime operating in the same units of base::TimeTicks and correctly handling NaN values. • Adjusted start time of scroll-linked animations when playback rate is updated. Bug: 852475 Change-Id: Iffd966c1b3ef6d821eef7cc2f6f79dae790a69f3 Reviewed-on: https://chromium-review.googlesource.com/c/1461513 Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com> Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#636836} -- wpt-commits: 6d7b2c196fceae37fd71c34f47b33ec7cc12eb0e wpt-pr: 15336
ea8a540c454f69264cfa65988a5e3fdf5de8e813: Bug 1534490 [wpt PR 15738] - Revert "Add test to check rendering of children of mspace", a=testonly
Frédéric Wang <fred.wang@free.fr> - Tue, 26 Mar 2019 14:04:52 +0000 - rev 467279
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534490 [wpt PR 15738] - Revert "Add test to check rendering of children of mspace", a=testonly Automatic update from web-platform-tests Revert "Add test to check rendering of children of mspace" -- wpt-commits: 6693cdfab4e7dc0fa7de7a737ecc60beedc02388 wpt-pr: 15738
97704c4611bacca3b994c871fe696c5412afaffe: Bug 1534244 [wpt PR 15722] - Add test to check rendering of children of mspace, a=testonly
Rob Buis <rbuis@igalia.com> - Tue, 26 Mar 2019 14:04:49 +0000 - rev 467278
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534244 [wpt PR 15722] - Add test to check rendering of children of mspace, a=testonly Automatic update from web-platform-tests Add test to check rendering of children of mspace -- Add tests for creating mfrac children dynamically Also add some edge cases (zero/one/more than two mfrac children). -- Merge pull request #15722 from rwlbuis/master Add test to check rendering of children of mspace -- wpt-commits: 6acb8d4420b969fc3cb5a2a64a2715be677828a0, 3fd81c19a5df597135d84595e0f316fd8128f85d, c8b23696067df3de626159f0a0ecdcbcaad605db wpt-pr: 15722
ccf17396dbe4ed6e47fe699902f6a0f10db9d6b5: Bug 1534489 [wpt PR 15736] - IndexedDB: Split bindings-inject-key.html test into 3 separate tests, a=testonly
Chase Phillips <cmp@chromium.org> - Tue, 26 Mar 2019 14:04:47 +0000 - rev 467277
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534489 [wpt PR 15736] - IndexedDB: Split bindings-inject-key.html test into 3 separate tests, a=testonly Automatic update from web-platform-tests IndexedDB: Split bindings-inject-key.html test into 3 separate tests Splitting this test will allow future test failures to be clearly assigned to a specific subtest. Bug: 934844 Change-Id: I2e62a27c5076c0564122b41f27b6fa2927bc11ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1504697 Commit-Queue: Chase Phillips <cmp@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#638939} -- wpt-commits: 5aa11068a1e4ebfc05d5184361dad4eaa1d6f897 wpt-pr: 15736
099ad90075bf65d9fa442ed1ee48b7fb11bed281: Bug 1532248 [wpt PR 15609] - Async Clipboard: Read/Write Blob->sequence<Blob>, a=testonly
Darwin Huang <huangdarwin@chromium.org> - Tue, 26 Mar 2019 14:04:37 +0000 - rev 467276
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1532248 [wpt PR 15609] - Async Clipboard: Read/Write Blob->sequence<Blob>, a=testonly Automatic update from web-platform-tests Async Clipboard: Read/Write Blob->sequence<Blob> - read(Blob) updated to read(sequence<Blob>). - write() returns sequence<Blob> instead of Blob now. - All available and valid types are returned in read() or allowed for write(). - Tests updated and added for these API changes. Also: - Updated header file function ordering. - Duplicate MIME types not allowed on write (consistent w/existing clipboard). Bug: 150835 Change-Id: I5b08e648a5313222552757dfa6fa0db6a7e46f68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1471492 Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#638905} -- wpt-commits: 3eb820dcc7cc5255f7182080caf9bd56f04d3cc2 wpt-pr: 15609
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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip