9b789837be4090a412637b9be0d9e5161e6f5d99: Bug 1572990 [wpt PR 18376] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 13 Aug 2019 19:52:42 +0000 - rev 488129
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1572990 [wpt PR 18376] - Update wpt metadata, a=testonly wpt-pr: 18376 wpt-type: metadata
967c3cc64306dfeb120276cca3c03cf694afde01: Bug 1572990 [wpt PR 18376] - [css-logical] WPTs for inset parsing, a=testonly
Eric Willigers <ericwilligers@chromium.org> - Wed, 14 Aug 2019 10:57:48 +0000 - rev 488128
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1572990 [wpt PR 18376] - [css-logical] WPTs for inset parsing, a=testonly Automatic update from web-platform-tests [css-logical] WPTs for inset parsing inset is one to four values, each auto or a length-percentage. https://drafts.csswg.org/css-logical/#propdef-inset Change-Id: I3f1599e200fec16a709cc6404246a28c404805b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1747488 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#686337} -- wpt-commits: 3b5944691d24e19a3937671885abb749334e8d45 wpt-pr: 18376
6b6dcecddad69c4c0663cf65a403a93a3f3d7a37: Bug 1572780 [wpt PR 18345] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 13 Aug 2019 19:42:11 +0000 - rev 488127
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1572780 [wpt PR 18345] - Update wpt metadata, a=testonly wpt-pr: 18345 wpt-type: metadata
7982193408a52625ab69541709d2bca93d9e6d64: Bug 1572780 [wpt PR 18345] - [ElementTiming] Fix background image loadTime, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Wed, 14 Aug 2019 10:57:39 +0000 - rev 488126
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1572780 [wpt PR 18345] - [ElementTiming] Fix background image loadTime, a=testonly Automatic update from web-platform-tests [ElementTiming] Fix background image loadTime This change adds a map |background_image_timestamps_| of load timestamps of background images tracked by StyleFetchedImage, which are the background images with url. The map only tracks the load time, as |images_notified_| must still be used to track the background image paints. Otherwise we'd only report an entry per background image even when applied to multiple elements. This change also makes computations a bit more efficient by only calling base::TimeTicks::Now() on the first time we load an entry. It also fixes a problem of calling Set() in between usages of an iterator, which is not allowed. Before this change, the added test would crash due to this problem. Bug: 879270, 986891 Change-Id: I86640f5587f69f94e13c429f3e55b3d5d6978cc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745497 Reviewed-by: Steve Kobes <skobes@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#686176} -- wpt-commits: 1d8fa760f9999ef13baa4c267bf042b7b4122789 wpt-pr: 18345
bae1cdaf20c87243d9da5bd5c633ad9175aa59bd: Bug 1573257 [wpt PR 18338] - Recreate XRInputSource when profiles change., a=testonly
Jacob DeWitt <jacde@chromium.org> - Wed, 14 Aug 2019 10:57:34 +0000 - rev 488125
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573257 [wpt PR 18338] - Recreate XRInputSource when profiles change., a=testonly Automatic update from web-platform-tests Recreate XRInputSource when profiles change. Based on discussion at https://github.com/immersive-web/webxr/issues/783 , we are confident this will become a requirement in the WebXR spec. Also update the OpenVR render loop to re-send the input source description when the profiles array is updated. Bug: 989244 Change-Id: I77bb2b15d894fe41c532235b062163bdc87a4ea2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1744663 Reviewed-by: Brian Sheedy <bsheedy@chromium.org> Reviewed-by: Brandon Jones <bajones@chromium.org> Commit-Queue: Jacob DeWitt <jacde@chromium.org> Cr-Commit-Position: refs/heads/master@{#686103} -- wpt-commits: f6819af5e6f4fa46c3c325faf2cfb060b2ac7914 wpt-pr: 18338
e4abe7c75be52ed20c1727eda0fdc6d0c7dd2676: Bug 1568104 [wpt PR 17989] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 23 Jul 2019 18:34:39 +0000 - rev 488124
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1568104 [wpt PR 17989] - Update wpt metadata, a=testonly wpt-pr: 17989 wpt-type: metadata
605be81220d91399bfa53fca37537b409f7b9d74: Bug 1568104 [wpt PR 17989] - Port WebSocket 3p-cookie-blocking web tests to wpt_internal, a=testonly
Lily Chen <chlily@chromium.org> - Wed, 14 Aug 2019 10:57:26 +0000 - rev 488123
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1568104 [wpt PR 17989] - Port WebSocket 3p-cookie-blocking web tests to wpt_internal, a=testonly Automatic update from web-platform-tests Port WebSocket 3p-cookie-blocking web tests to wpt_internal (For context, see https://crrev.com/c/1691522.) The new requirement that SameSite=None cookies must be Secure made it impossible to properly test third party cookies on WebSocket because the web_test runner does not have a wss server. This CL ports those tests, formerly in web_tests/http/tests/security/cookies/websocket/, to web_tests/wpt_internal/websocket-cookies/. Bug: none Change-Id: Ifc6d2d78a84aa6c93e297dc71b3595108a18f179 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713670 Commit-Queue: Lily Chen <chlily@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#686071} -- wpt-commits: 990925e0c2bd9100806e7fee202911444a71a7c7 wpt-pr: 17989
a2a802a992a07a69658c5e3daeab5ccdb1d40069: Bug 1568091 [wpt PR 17986] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 23 Jul 2019 01:22:13 +0000 - rev 488122
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1568091 [wpt PR 17986] - Update wpt metadata, a=testonly wpt-pr: 17986 wpt-type: metadata
e0a7d47faddb3ae446a4e81d51b515fa2a3ae3e8: Bug 1568091 [wpt PR 17986] - Add cookie SameSite features to experimental web platform features, a=testonly
Lily Chen <chlily@chromium.org> - Wed, 14 Aug 2019 10:57:18 +0000 - rev 488121
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1568091 [wpt PR 17986] - Add cookie SameSite features to experimental web platform features, a=testonly Automatic update from web-platform-tests Add cookie SameSite features to experimental web platform features SameSiteByDefaultCookies and CookiesWithoutSameSiteMustBeSecure, as well as CookieDeprecationMessages can now be turned on by running with command line flag --enable-experimental-web-platform-features. * SameSiteByDefaultCookies causes cookies that don't specify a SameSite attribute to be treated as Lax, and introduces SameSite=None to explicitly request cross-site use. * CookiesWithoutSameSiteMustBeSecure requires SameSite=None cookies to be Secure, otherwise they are rejected. * CookieDeprecationMessages shows console messages when cookies are not sent or saved due to either of the above SameSite features. The web tests and browser tests run with experimental web platform features enabled are also updated to reflect the new behavior, including running on https because of the CookiesWithoutSameSiteMustBeSecure restriction. This also adds SameSite=None test coverage to a couple places that didn't already have it. Bug: 953306, 954551, 961439 Change-Id: I50ea7a6fb73969acf9ba3088310d7d246bc11a05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691522 Commit-Queue: Lily Chen <chlily@chromium.org> Reviewed-by: Rick Byers <rbyers@chromium.org> Reviewed-by: John Abd-El-Malek <jam@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Reviewed-by: Maks Orlovich <morlovich@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#686029} -- wpt-commits: de517e33fddfc1ee979ae23ebb9ef954a766bcf2 wpt-pr: 17986
6dadd5a887df764d0842af4ca9866a54317d6bff: Bug 1573224 [wpt PR 18339] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 13 Aug 2019 19:05:14 +0000 - rev 488120
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573224 [wpt PR 18339] - Update wpt metadata, a=testonly wpt-pr: 18339 wpt-type: metadata
de0528635d593db5e09eb5119b0c4bb12c0b0d15: Bug 1573224 [wpt PR 18339] - Expose XRVisibilityState, a=testonly
Brandon Jones <bajones@chromium.org> - Wed, 14 Aug 2019 10:57:10 +0000 - rev 488119
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573224 [wpt PR 18339] - Expose XRVisibilityState, a=testonly Automatic update from web-platform-tests Expose XRVisibilityState Replaces the previous XRSession "blur" and "focus" events with the visibilityState attribute and an associated "visibilitychange" event. Bug: 987030 Change-Id: I1d60dd50102b4d3be583ae023cad8994ab17b01b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1744650 Reviewed-by: Brian Sheedy <bsheedy@chromium.org> Reviewed-by: Klaus Weidner <klausw@chromium.org> Commit-Queue: Brandon Jones <bajones@chromium.org> Cr-Commit-Position: refs/heads/master@{#686040} -- wpt-commits: 033cff019de41220b9446661ee5527e7475d27e1 wpt-pr: 18339
37fa0d77d7385e795c8d4ad3d12b3bb047808411: Bug 1573203 [wpt PR 18391] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 13 Aug 2019 18:55:59 +0000 - rev 488118
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573203 [wpt PR 18391] - Update wpt metadata, a=testonly wpt-pr: 18391 wpt-type: metadata
74a2012e3573c4725ed808e9dd18e29d0ecf2d8c: Bug 1573203 [wpt PR 18391] - Add tests to prevent a sandbox iframe from using history APIs, a=testonly
Dave Tapuska <dtapuska@chromium.org> - Wed, 14 Aug 2019 10:57:02 +0000 - rev 488117
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573203 [wpt PR 18391] - Add tests to prevent a sandbox iframe from using history APIs, a=testonly Automatic update from web-platform-tests Add tests to prevent a sandbox iframe from using history APIs Spec change https://github.com/whatwg/html/pull/4787 BUG=705583 Change-Id: I6fc5fee627156c10c771b63b609d1d25c6fd439c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749444 Reviewed-by: Domenic Denicola <domenic@chromium.org> Commit-Queue: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/master@{#686032} -- wpt-commits: 5d435e04f41adf7c891c575b3f8ab120923766fe wpt-pr: 18391
b9780850967fe06ee0e91cf86d055554d69996f2: Bug 1572755 [wpt PR 18356] - Fix bug where composite: replace did not replace previous effects, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 14 Aug 2019 10:56:48 +0000 - rev 488116
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1572755 [wpt PR 18356] - Fix bug where composite: replace did not replace previous effects, a=testonly Automatic update from web-platform-tests Fix bug where composite: replace did not replace previous effects Consider a set of effects: e.animate([{ "width": "0" }, { "width": "5px" }], { duration: 100 }); e.animate([{ "width": "0" }, { "width": "5px" }], { duration: 100, composite: 'add' }); e.animate([{ "width": "0" }, { "width": "2px" }], { duration: 100 }); e.animate([{ "width": "0" }, { "width": "2px" }], { duration: 100, composite: 'add' }); Previously the code in CopyToActiveInterpolationsMap would incorrectly move the third effect to the start of the list to replace the original keyframe pair, resulting in an effect stack of: { "width": "0" }, { "width": "2px" } { "width": "0" }, { "width": "5px" } { "width": "0" }, { "width": "2px" } This is wrong; not only has it retained an effect it shouldn't have, it has also re-ordered keyframes which might break non-commutative additive properties. This CL fixes the logic to properly clear out existing effects when a composite: 'replace' effect is put onto the stack. Bug: 992378 Change-Id: I94ae54429ac7d4d28a0702d397ab64c2e45dee65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746302 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#686024} -- wpt-commits: a851a6a8e8b11160bcd6f5861553cf8419258136 wpt-pr: 18356
1054904199286a37d07e4cf547e3370d312337b2: Bug 1572792 [wpt PR 18343] - [docs] Improve submission guidelines, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Wed, 14 Aug 2019 10:56:43 +0000 - rev 488115
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1572792 [wpt PR 18343] - [docs] Improve submission guidelines, a=testonly Automatic update from web-platform-tests [docs] Reorganize information on test submission Relocate README content relevant pages within the documentation site, split apart according to the intended audience. -- [docs] Streamline information on test submission Recommend the detailed "Introduction to GitHub" prior to summarizing the preferred workflow to more quickly support readers who need additional guidance. Shorten the summarized steps to more efficiently direct readers who are familiar with the process. -- [docs] Document requirement for PR approval -- [docs] Remove conflicting use of term "upstream" The term "upstream" is typically reserved for the canonical version of the source code. Replace usages which contradict that meaning with a less specific term, "trusted fork." -- [docs] Remove duplicated content -- [docs] Improve link text -- wpt-commits: 18a159fb46bf3966b5bb1f589e24df10495a6d10, bbc9fe01d21d83458a4a7897a2e83b87a96fff18, a4d0ede58d7c43bc108c9c5b5cc6fc29de6dfb67, 0bd47344377f14bceb09b64448c86289e1ac0265, 44cbd35cae868b0d2948978d77af1e6324e9a407, 2ae2a10e2c4272baca94374b2ce644084e89bf98 wpt-pr: 18343
32daa44117d0be2030a8ac6bae0e6893da18963d: Bug 1571940 [wpt PR 18304] - [docs] Explain behavior of failing assertions, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Wed, 14 Aug 2019 10:56:38 +0000 - rev 488114
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1571940 [wpt PR 18304] - [docs] Explain behavior of failing assertions, a=testonly Automatic update from web-platform-tests [docs] Explain behavior of failing assertions The mechanism that assertions use to signal failure influences test design and is therefore relevant to test authors. -- wpt-commits: 1812d81b14f0d81799370beb04f744d3c113a9ca wpt-pr: 18304
afb522e14cdc327f605c3c465c5e58fbcfd5c977: Bug 1571938 [wpt PR 18303] - [docs] Document and test testharness.js utility fn, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Wed, 14 Aug 2019 10:56:33 +0000 - rev 488113
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1571938 [wpt PR 18303] - [docs] Document and test testharness.js utility fn, a=testonly Automatic update from web-platform-tests [docs] Document and test testharness.js utility fn -- wpt-commits: 35a5c1fad24d4a40d21cc4639f542fdd5b37e558 wpt-pr: 18303
565b9d7d08dd8a87c37219405e433d2466a45a38: Bug 1573092 [wpt PR 18383] - Update interfaces/notifications.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 14 Aug 2019 10:56:27 +0000 - rev 488112
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573092 [wpt PR 18383] - Update interfaces/notifications.idl, a=testonly Automatic update from web-platform-tests Update interfaces/notifications.idl (#18383) Source: https://github.com/tidoust/reffy-reports/blob/3336bd0/whatwg/idl/notifications.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/570123391 -- wpt-commits: 1e549970b5b3159bd6ea40cf1e6cf8f8a1d821f4 wpt-pr: 18383
d66154dc0b98284caa2fa5daff853eafc3066bad: Bug 1573150 [wpt PR 18387] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 13 Aug 2019 22:25:32 +0000 - rev 488111
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573150 [wpt PR 18387] - Update wpt metadata, a=testonly wpt-pr: 18387 wpt-type: metadata
1e63e0974c28c5978d9953285edda9a2cb5e1f7c: Bug 1573150 [wpt PR 18387] - Translate svg/animation tests to WPT (Commit 4), a=testonly
Edvard Thörnros <edvardt@opera.com> - Wed, 14 Aug 2019 10:56:19 +0000 - rev 488110
Push 36435 by cbrindusan@mozilla.com at Thu, 15 Aug 2019 09:46:49 +0000
Bug 1573150 [wpt PR 18387] - Translate svg/animation tests to WPT (Commit 4), a=testonly Automatic update from web-platform-tests Translate svg/animation tests to WPT (Commit 4) This is the forth commit in the series of updating all the old svg animation tests. The usage of testharness has replaced the older SVGAnimationTest.js for all where it's suitable. No functionality should have changed and the tests should cover almost the same. In all of the animations where there is a sampling at T=0, where it was assumed that no animations had started. Which didn't work flawlessly when moved to the new system, it has thus been removed. Bug: 985335 Change-Id: I1ac61d1fda2cc3de76e1a23cda06e76e8819d307 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746004 Auto-Submit: Edvard Thörnros <edvardt@opera.com> Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#685981} -- wpt-commits: 732186f624aac2ccfe1c82cc304fd91ee10f2418 wpt-pr: 18387
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip