c9aeb07be8ce287b47a1e64e9d47d4ecaccff393: Bug 1600675 [wpt PR 20559] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 05 Dec 2019 13:36:35 +0000 - rev 506050
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1600675 [wpt PR 20559] - Update wpt metadata, a=testonly wpt-pr: 20559 wpt-type: metadata
eb7a4f2205da527efe02f606f04b0958eccd4656: Bug 1600675 [wpt PR 20559] - Update reversing-an-animation test, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Thu, 05 Dec 2019 15:50:34 +0000 - rev 506049
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1600675 [wpt PR 20559] - Update reversing-an-animation test, a=testonly Automatic update from web-platform-tests Update reversing-an-animation test (#20559) Double rAF start of the test to avoid starting the animation while too busy to handle updates in a timely manner. Bug: 1029541 Change-Id: I3e0e665f0b4b9dd6f6a87d84d207b0c18a1b51c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946668 Commit-Queue: Kevin Ellis <kevers@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#721486} -- wpt-commits: 85a8c5a0ee860c22562eab683858703fe66d8872 wpt-pr: 20559
17752c46a85f4980cbd9237fb9f14a3247da2d94: Bug 1598599 [wpt PR 20394] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 05 Dec 2019 13:20:47 +0000 - rev 506048
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1598599 [wpt PR 20394] - Update wpt metadata, a=testonly wpt-pr: 20394 wpt-type: metadata
90f7cca023be748e7338a635b6c4563a7dbcdd74: Bug 1598599 [wpt PR 20394] - `CredentialsContainer::IsSameOriginWithAncestors` should ignore `domain`., a=testonly
Mike West <mkwst@chromium.org> - Thu, 05 Dec 2019 15:50:26 +0000 - rev 506047
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1598599 [wpt PR 20394] - `CredentialsContainer::IsSameOriginWithAncestors` should ignore `domain`., a=testonly Automatic update from web-platform-tests `CredentialsContainer::IsSameOriginWithAncestors` should ignore `domain`. Per [1], we should be performing a "same origin" check, not a "same origin-domain" check. [1]: https://w3c.github.io/webappsec-credential-management/#same-origin-with-its-ancestors Bug: 1027476 Change-Id: I58be7f6c471848bf7f8f860bfa9895c101e03192 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930797 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#721976} -- wpt-commits: 163137f3d25bb13ea01a86cbdc863d089101f5ec wpt-pr: 20394
0263b17f8d0b02ec6a594eae3e86eab64edd89ea: Bug 1601545 [wpt PR 20627] - cc Fix bad media condition in picture[sizes] test, a=testonly
Michael[tm] Smith <mike@w3.org> - Thu, 05 Dec 2019 15:50:21 +0000 - rev 506046
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601545 [wpt PR 20627] - cc Fix bad media condition in picture[sizes] test, a=testonly Automatic update from web-platform-tests cc Fix bad media condition in picture[sizes] test Also, add a <!-- DO NOT EDIT! ... --> comment to all generated files. Fixes https://github.com/web-platform-tests/wpt/issues/20628 See https://github.com/w3c/css-validator/issues/266#issuecomment-561786647 -- wpt-commits: 6072f32a8ce1bc20f1a08ea8f4308cdb7fda3165 wpt-pr: 20627
d7ca7591dfa96cd134f96c6a34d98a5ad44b00fb: Bug 1601352 [wpt PR 20614] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 05 Dec 2019 10:36:29 +0000 - rev 506045
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601352 [wpt PR 20614] - Update wpt metadata, a=testonly wpt-pr: 20614 wpt-type: metadata
931d4d6e253bc987fac9ded9713d27a9811ededc: Bug 1601352 [wpt PR 20614] - [Trusted Types] Add tt.emptyScript., a=testonly
Stefano Sanfilippo <ssanfilippo@chromium.org> - Thu, 05 Dec 2019 15:50:09 +0000 - rev 506044
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601352 [wpt PR 20614] - [Trusted Types] Add tt.emptyScript., a=testonly Automatic update from web-platform-tests [Trusted Types] Add tt.emptyScript. Change-Id: I3ba7da30f4e1baeeabb75f74991434c4b573e660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1950537 Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Auto-Submit: Stefano Sanfilippo <ssanfilippo@chromium.org> Cr-Commit-Position: refs/heads/master@{#721934} -- wpt-commits: 1c107d5bb86e9a5f2d387ccff599c43ed46bc864 wpt-pr: 20614
eb7580fba601fc505c15532bc9d7e8dfe2c5aadd: Bug 1601514 [wpt PR 20624] - Fixed not lazily loading for explicit loading=lazy image, a=testonly
Wanchang Ryu <wanchang.ryu@lge.com> - Thu, 05 Dec 2019 15:50:04 +0000 - rev 506043
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601514 [wpt PR 20624] - Fixed not lazily loading for explicit loading=lazy image, a=testonly Automatic update from web-platform-tests Fixed not lazily loading for explicit loading=lazy image Previously when a image element is invisible, it loads image eagerly for both 'auto' and 'lazy' by https://chromium-review.googlesource.com/c/chromium/src/+/1668710 But when attribute is set 'lazy' explicitly, we can still use lazy loading because lazy loading is intended. Bug: 1027153 Change-Id: Ibb0ad782049c66863d242d929f1e94fa6ddd1ed0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1950104 Reviewed-by: Dominic Farolino <dom@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Scott Little <sclittle@chromium.org> Commit-Queue: Wanchang Ryu <wanchang.ryu@lge.com> Cr-Commit-Position: refs/heads/master@{#721911} -- wpt-commits: 89f3dc2dcebe5bc12916672970d2b21609438e27 wpt-pr: 20624
607a2735104025511e2136549cbdd026fffa0095: Bug 1601236 [wpt PR 20602] - Add shallawa to svg/META.yml, a=testonly
Simon Pieters <zcorpan@gmail.com> - Thu, 05 Dec 2019 15:49:59 +0000 - rev 506042
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601236 [wpt PR 20602] - Add shallawa to svg/META.yml, a=testonly Automatic update from web-platform-tests Add shallawa to svg/META.yml (#20602) -- wpt-commits: 74884d2f3a9031839bad0f143529dc4de47cdb51 wpt-pr: 20602
d6491d87544ad69adcd1ff7be9ca0c65ba91f717: Bug 1601085 [wpt PR 20597] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 05 Dec 2019 01:37:41 +0000 - rev 506041
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601085 [wpt PR 20597] - Update wpt metadata, a=testonly wpt-pr: 20597 wpt-type: metadata
2577a07481238c0b05b2fda4275cd675bd57d747: Bug 1601085 [wpt PR 20597] - Add additional WPT tests for new cases of KeyframeEffect.target and .pseudoElement, a=testonly
George Steel <gtsteel@google.com> - Thu, 05 Dec 2019 15:49:52 +0000 - rev 506040
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601085 [wpt PR 20597] - Add additional WPT tests for new cases of KeyframeEffect.target and .pseudoElement, a=testonly Automatic update from web-platform-tests Add additional WPT tests for new cases of KeyframeEffect.target and .pseudoElement Goes with spec CL https://github.com/w3c/csswg-drafts/pull/4437 (merged) Follows up on https://crrev.com/c/1894477 Change-Id: I9f50739cb4dac68d3c9002c0f3ed509f6b379380 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949405 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Kevin Ellis <kevers@chromium.org> Commit-Queue: George Steel <gtsteel@chromium.org> Cr-Commit-Position: refs/heads/master@{#721752} -- wpt-commits: 6439c341d31a4a4695cec8a90ac18f5365547c79 wpt-pr: 20597
b20ab23b0bef3f34f9d7b06d8fd08fc84a3b7d24: Bug 1594915 [wpt PR 20162] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 04 Dec 2019 22:37:37 +0000 - rev 506039
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1594915 [wpt PR 20162] - Update wpt metadata, a=testonly wpt-pr: 20162 wpt-type: metadata
405f97bc42e5cb699a63140ce9d2d31b7a31207c: Bug 1594915 [wpt PR 20162] - Implement WebAuthn basic test using testdriver API, a=testonly
Nina Satragno <nsatragno@gmail.com> - Thu, 05 Dec 2019 15:49:44 +0000 - rev 506038
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1594915 [wpt PR 20162] - Implement WebAuthn basic test using testdriver API, a=testonly Automatic update from web-platform-tests Implement WebAuthn basic test using testdriver API (#20162) * Implement WebAuthn basic test using testdriver API This change adds a test for successfully creating a credential and getting an assertion, automated using the testdriver.js WebAuthn API. * nits. -- wpt-commits: eca8c168b2cb04f3f1bf223ca653640df7933c58 wpt-pr: 20162
d40d8e7f2725566e192bc7d463d058e5af622fef: Bug 1601012 [wpt PR 20588] - Revert "[LayoutNG] Set ShrinkToFit when determining MinMaxSize via layout", a=testonly
David Grogan <dgrogan@chromium.org> - Thu, 05 Dec 2019 15:49:34 +0000 - rev 506037
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601012 [wpt PR 20588] - Revert "[LayoutNG] Set ShrinkToFit when determining MinMaxSize via layout", a=testonly Automatic update from web-platform-tests Revert "[LayoutNG] Set ShrinkToFit when determining MinMaxSize via layout" This reverts commit 4fb5e9ecba28a18c69ef4736cce74664ae82af6a. Reason for revert: Triggered DCHECK !constraint_space.IsIntermediateLayout() || box_->NeedsLayout() Original change's description: > [LayoutNG] Set ShrinkToFit when determining MinMaxSize via layout > > Bug: 635619 > Change-Id: I6f7b1e16098a773aab2ac395b3b23e8b2af2b99e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1920200 > Reviewed-by: Morten Stenshorne <mstensho@chromium.org> > Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> > Commit-Queue: David Grogan <dgrogan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#716907} TBR=cbiesinger@chromium.org,dgrogan@chromium.org,mstensho@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 635619, 1027759 Change-Id: I961ca71602f331d2a612d430e9a4ae049e331b1c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948496 Reviewed-by: David Grogan <dgrogan@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#721112} -- wpt-commits: a1e081b3bb42c20186d3dfc3650e973bc0141899 wpt-pr: 20588
29b7257d966c8284fa6bb4104722ce5c490c3863: Bug 1600956 [wpt PR 20585] - [LayoutNG] Set column fragments to the actual column size., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 05 Dec 2019 15:49:29 +0000 - rev 506036
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1600956 [wpt PR 20585] - [LayoutNG] Set column fragments to the actual column size., a=testonly Automatic update from web-platform-tests [LayoutNG] Set column fragments to the actual column size. Just letting the fragmentation machinery do what it would do if it gets to treat column boxes as regular column content was no conscious choice, and it turns out that setting the column fragments to the actual column size is better, or we get some trouble with overflow, both when it comes to painting column rules, and the fact that we get spurious empty column fragments after unbreakable content (new unit test NGColumnLayoutAlgorithmTest.TallReplacedContent). Remove fast/multicol/rule-in-nested-with-too-tall-line.html and replace it with a valid test (that still fails both in legacy and NG; in NG because we fail to paint text on a general basis). Bug: 829028 Change-Id: I3656c299c7a87bea29e1790477cf524b9522fa97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948923 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#721376} -- wpt-commits: 54a6679265caf957a1470c2b398a81bd5440dd2f wpt-pr: 20585
7277b0014a897760410157bd187abd04781a3dfa: Bug 1601137 [wpt PR 20600] - Adjust infinite-scroll-event to pass., a=testonly
Chris Harrelson <chrishtr@chromium.org> - Thu, 05 Dec 2019 15:49:24 +0000 - rev 506035
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601137 [wpt PR 20600] - Adjust infinite-scroll-event to pass., a=testonly Automatic update from web-platform-tests Adjust infinite-scroll-event to pass. scrollTopMax is not a standardized web feature. The actual functionality was passing as of: https://chromium.googlesource.com/chromium/src/+/6a9dd6d26726f346345cf1970c2bc3af3ec1afbd Bug: 997502 Change-Id: Ic120d09d0e6a9652c195afe0ac7cacece917dd47 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949556 Reviewed-by: Nick Burris <nburris@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#721318} -- wpt-commits: 3f1485cc2793f55236076dfffc3c3fa69315e101 wpt-pr: 20600
ddb081f1c0659a2b99a13b41d64e6b0cc18c9e2c: Bug 1601075 [wpt PR 20595] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 04 Dec 2019 03:23:36 +0000 - rev 506034
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601075 [wpt PR 20595] - Update wpt metadata, a=testonly wpt-pr: 20595 wpt-type: metadata
a13898cb3364862002fb9de0e58f039c4c0a5b3e: Bug 1601075 [wpt PR 20595] - [Longtasks] Fix containerType and containerSrc in attribution, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Thu, 05 Dec 2019 15:49:16 +0000 - rev 506033
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1601075 [wpt PR 20595] - [Longtasks] Fix containerType and containerSrc in attribution, a=testonly Automatic update from web-platform-tests [Longtasks] Fix containerType and containerSrc in attribution This CL brings the longtasks API up to date with the recent changes on https://github.com/w3c/longtasks/pull/78. It also adds WPT tests for those changes. The changes are: * containerType is "window", "iframe", "embed", etc. depending on the type of the culprit browsing context container. * containerSrc is now the 'data' attribute when the container is an <object>. Change-Id: I06f661968778e3bec433a1bfe758b4604df01557 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949146 Reviewed-by: Steve Kobes <skobes@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#721258} -- wpt-commits: e92918c7452f2ef99fe95545fdfb41a7787b9b94 wpt-pr: 20595
015d75b07dd8f355e2540830a52ef52fcaecf203: Bug 1598794 [wpt PR 20413] - Don't enqueue a scroll event for clamping or anchoring scrolls if not changed., a=testonly
Chris Harrelson <chrishtr@chromium.org> - Thu, 05 Dec 2019 15:49:11 +0000 - rev 506032
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1598794 [wpt PR 20413] - Don't enqueue a scroll event for clamping or anchoring scrolls if not changed., a=testonly Automatic update from web-platform-tests Don't enqueue a scroll event for clamping or anchoring scrolls if not changed. Other scroll types will still directly enqueue a scroll event. Forced layouts may cause scroll offset changes that are undone by later updates. There is no spec that requires the current behavior as far as I can tell. The CSSOM spec calls out that it should fire "when the viewport or element is scrolled" [1] [1] https://drafts.csswg.org/cssom-view/#eventdef-document-scroll Bug: 988991 Change-Id: I4e4ebcf2c5bcba8111d73ebd0b2b8a037034caaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928243 Reviewed-by: Nick Burris <nburris@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#721247} -- wpt-commits: f05d61183a22708b4aa4a0c57bd06bab813cb0ec wpt-pr: 20413
ccb7dc5e93d1c3ac86c37c60af353c3fda36eab9: Bug 1600851 [wpt PR 20574] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 04 Dec 2019 03:30:40 +0000 - rev 506031
Push 36895 by ccoroiu@mozilla.com at Mon, 09 Dec 2019 16:35:51 +0000
Bug 1600851 [wpt PR 20574] - Update wpt metadata, a=testonly wpt-pr: 20574 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip