9504c257191615f9a40dd9ba98589eddd7da5c4a: Bug 1565587 [wpt PR 14914] - LazyLoad: Add external web platform tests for the "loading" attribute., a=testonly
rajendrant <rajendrant@chromium.org> - Mon, 22 Jul 2019 11:05:54 +0000 - rev 484319
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565587 [wpt PR 14914] - LazyLoad: Add external web platform tests for the "loading" attribute., a=testonly Automatic update from web-platform-tests LazyLoad: Add external web platform tests for the "loading" attribute. This CL includes tests for: - Testing that images and iframes with the attribute loading="lazy" are deferred until they come into view - Testing that images and iframes with the attribute loading="eager" are loaded immediately Bug: 916260 Change-Id: I323faa31c7683663d0d0136a719cf83c25758ad6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1417117 Commit-Queue: Dominic Farolino <dom@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Tarun Bansal <tbansal@chromium.org> Reviewed-by: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#676804} -- wpt-commits: 9919d0f04266001686c09d47ff6e25c98b48d91f wpt-pr: 14914
b17e5baf4622707dff258f39231d1d940dcefbfd: Bug 1565450 [wpt PR 17799] - [cssom] getComputedStyle not getComputedValue, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Mon, 22 Jul 2019 11:05:49 +0000 - rev 484318
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565450 [wpt PR 17799] - [cssom] getComputedStyle not getComputedValue, a=testonly Automatic update from web-platform-tests [cssom] getComputedStyle not getComputedValue (#17799) Fix typo in test titles. -- wpt-commits: 9daa6ffd6eb28afb0940b7ac304b08e8383fc527 wpt-pr: 17799
80980de0d935b127c7a9769581f9848f4be5d853: Bug 1565299 [wpt PR 17779] - CSS property 'tab-size' should take 'number' instead of 'integer'., a=testonly
Joonghun Park <pjh0718@gmail.com> - Mon, 22 Jul 2019 11:05:43 +0000 - rev 484317
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565299 [wpt PR 17779] - CSS property 'tab-size' should take 'number' instead of 'integer'., a=testonly Automatic update from web-platform-tests CSS property 'tab-size' should take 'number' instead of 'integer'. According to https://drafts.csswg.org/css-text-3/#tab-size-property, let 'tab-size' take css 'number' value, not css 'integer' value. Bug: 974090 Change-Id: Idb235eacde59f5bae1ab7fb814425fae4b93a227 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1689165 Commit-Queue: Joonghun Park <pjh0718@gmail.com> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#676741} -- wpt-commits: 01669b3a69c55c077a6f5212c295528c89388d6c wpt-pr: 17779
99dd0ca98c47cf37ebe24d7a9c4be0ba0bae10f7: Bug 1565442 [wpt PR 15319] - [compositing] Computed value tests, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Mon, 22 Jul 2019 11:05:38 +0000 - rev 484316
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565442 [wpt PR 15319] - [compositing] Computed value tests, a=testonly Automatic update from web-platform-tests [compositing] Computed value tests (#15319) background-blend-mode, isolation, mix-blend-mode computed values are as specified. https://drafts.fxtf.org/compositing-1/#property-index All tests pass with Firefox. Three background-blend-mode tests fail with Blink/Edge/Safari: expected "normal, luminosity" but got "normal" expected "screen, overlay" but got "screen" expected "color, saturation" but got "color" -- wpt-commits: d0a227ec363d652a133d53bdda7ab2ef976e6008 wpt-pr: 15319
d1202053834625c62e03fe32037c7d2676adad3f: Bug 1565432 [wpt PR 17797] - [docs] Normalize spelling of "test suite", a=testonly
Mike Pennisi <mike@mikepennisi.com> - Mon, 22 Jul 2019 11:05:33 +0000 - rev 484315
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565432 [wpt PR 17797] - [docs] Normalize spelling of "test suite", a=testonly Automatic update from web-platform-tests [docs] Normalize spelling of "test suite" The documentation uses the terms "testsuite" and "test suite" interchangeably. Normalize on "test suite." -- wpt-commits: 03fcaec457809e26a282727951c155b82660e159 wpt-pr: 17797
c7280523d8ffa8d6eda07c97bf2282bb8ab826d9: Bug 1565408 [wpt PR 17796] - [docs] Correct internal links, a=testonly
jugglinmike <mike@mikepennisi.com> - Mon, 22 Jul 2019 11:05:28 +0000 - rev 484314
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565408 [wpt PR 17796] - [docs] Correct internal links, a=testonly Automatic update from web-platform-tests [docs] Correct internal links (#17796) -- wpt-commits: d3d45d7d0e1bd20653a4f9880c0229cb5c80ceb1 wpt-pr: 17796
8059ecb55960508be52e715448345f90c7827c31: Bug 1565366 [wpt PR 17784] - Sync Mozilla CSS tests as of 2019-07-11, a=testonly
L. David Baron <dbaron@dbaron.org> - Mon, 22 Jul 2019 11:05:23 +0000 - rev 484313
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565366 [wpt PR 17784] - Sync Mozilla CSS tests as of 2019-07-11, a=testonly Automatic update from web-platform-tests Sync Mozilla CSS tests as of https://hg.mozilla.org/mozilla-central/rev/a39b925a26ade6f6d05c51dde62764b149043a00 . This contains changes from one bug: * [bug 1559276](https://bugzilla.mozilla.org/show_bug.cgi?id=1559276), by @BorisChiou, reviewed by @emilio -- wpt-commits: 1f951fe9e702fa19c10d4c74efa79c741b452cd1 wpt-pr: 17784
db22cb4117b92f1d46b23d9c3aa2313cad943126: Bug 1565402 [wpt PR 17634] - [docs] Expand landing page, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Mon, 22 Jul 2019 11:05:17 +0000 - rev 484312
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565402 [wpt PR 17634] - [docs] Expand landing page, a=testonly Automatic update from web-platform-tests [docs] Expand landing page Currently, the documentation website's landing page contains only a table of contents. The introductory material is accessible through the first link in that index. Because the landing page is itself an introduction, it ought to offer some explanation of the project's purpose and structure. Re-use the introductory text found in the project's README.md file since this is slightly more complete than the corresponding text in the "introduction" page. Move other high-level information to the landing page and rename the "introduction" to "testsuite design" in order to better describe its more narrow focus. -- [docs] Correct typos -- wpt-commits: f3cdfbcb428ca2f711d0b5128264d3f7cfcfd187, 6d60c3d31206401a3e22db74c68429a302443d9f wpt-pr: 17634
e25261038370c248b074ad924319d931ca1ab37d: Bug 1558363 [wpt PR 17785] - [Gecko Bug 1558363] Fix WPT manifest updates when within a git tree, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 22 Jul 2019 11:01:26 +0000 - rev 484311
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1558363 [wpt PR 17785] - [Gecko Bug 1558363] Fix WPT manifest updates when within a git tree, a=testonly Automatic update from web-platform-tests Fix WPT manifest updates when within a git tree This has been broken since bug 1545629 landed, when we started using git to (quickly) get hashes of unchanged files. Unfortunately, the logic for finding changed files only worked when the test root was the root of the git repository. Differential Revision: https://phabricator.services.mozilla.com/D34702 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1558363 gecko-commit: b975b4c1dfaebedabc4a09296b90303c7d5381e3 gecko-integration-branch: central gecko-reviewers: jgraham -- wpt-commits: 3fb0150bb0a53b5a6630e8eda7f43bf75d8a6bbe wpt-pr: 17785
143a99f983d1e2567c0c976f376ee0bc763371ea: Bug 1558831 [wpt PR 17295] - Move movementX/Y calculation for aura pointer-locked state to Blink., a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Mon, 22 Jul 2019 10:25:19 +0000 - rev 484310
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1558831 [wpt PR 17295] - Move movementX/Y calculation for aura pointer-locked state to Blink., a=testonly Automatic update from web-platform-tests Move movementX/Y calculation for aura pointer-locked state to Blink. (#17295) This change moves movementX/Y calculation for aura pointer-locked state to Blink. On aura, pointer lock use "move to center" to make cursor stays in the window. With the calculation done in blink side, the move to center event is marked as synthesize move, so that we can update the blink side states and do not dispatch the event. The change is under content feature flag kConsolidatedMovementXY Bug: 802067 Change-Id: I05360dadd18a2f41481a0de9ef78a05199493857 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618306 Commit-Queue: Ella Ge <eirage@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#674237} -- wpt-commits: 293143370ddaa9ceaee4294c78a17d97e7bdd5c6 wpt-pr: 17295
46bfb47184833e41af88b8a87e66cb7a3dbc4669: Bug 1565046 [wpt PR 17773] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 11 Jul 2019 21:47:45 +0000 - rev 484309
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565046 [wpt PR 17773] - Update wpt metadata, a=testonly wpt-pr: 17773 wpt-type: metadata
809c03bd3d96167317836f5650efa308a68610fd: Bug 1565046 [wpt PR 17773] - [UserTimingL3] Fix crash: create mark in worker, a=testonly
Liquan(Max) Gu <maxlg@chromium.org> - Mon, 22 Jul 2019 10:25:08 +0000 - rev 484308
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565046 [wpt PR 17773] - [UserTimingL3] Fix crash: create mark in worker, a=testonly Automatic update from web-platform-tests [UserTimingL3] Fix crash: create mark in worker Currently, the renderer crashes when creating mark entry in worker. The crash is because PerformanceMark::Create() return nullptr without setting exception_state. The caller of the function assumes that no exception indicates the PerformanceMark entry exists. Thus, when the entry is visited, the crash occurs. There is another bug hidden in this issue. Currently, when window-performance is not found, Create() returns nullptr directly. It should instead also check whether worker-performance exist. This CL fix these issues. To verify the change, the CL also changes the related web tests from *.html to *.any.js, which enables these tests in worker's context. Bug: 981982 Change-Id: Ia20ce1c194e4db2810ff3f1c52070e5970951600 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696085 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#676484} -- wpt-commits: 133323811602dd4ceced46f11aabb645a3582983 wpt-pr: 17773
e1fec2bf3959430641d7cbd6cc628ba92faaad40: Bug 1565376 [wpt PR 17780] - Create toast action setter, a=testonly
Jack Steinberg <jacksteinberg@chromium.org> - Mon, 22 Jul 2019 10:25:03 +0000 - rev 484307
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565376 [wpt PR 17780] - Create toast action setter, a=testonly Automatic update from web-platform-tests Create toast action setter Additionally, this CL adds support for passing Elements as action in showToast, using the action setter. This change is the latest in a series of changes implementing new behavior added to the toast explainer in PR #43 https://github.com/jackbsteinberg/std-toast/pull/43. Bug: 972945 Change-Id: I46004883cb3b794981029aa02369918dd0077391 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1686786 Commit-Queue: Jack Steinberg <jacksteinberg@chromium.org> Reviewed-by: Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#676482} -- wpt-commits: 11051ca7a0270ae8fe07939d35cd923e5b542748 wpt-pr: 17780
0d91dc041eaef73b3518dcde8ed455df55619914: Bug 1565061 [wpt PR 17775] - Partially fix calc() length unit handling in media queries, a=testonly
Xiaocheng Hu <xiaochengh@chromium.org> - Mon, 22 Jul 2019 10:24:57 +0000 - rev 484306
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565061 [wpt PR 17775] - Partially fix calc() length unit handling in media queries, a=testonly Automatic update from web-platform-tests Partially fix calc() length unit handling in media queries When a calc() length is passed to media queries, the current code assumes that there's always a DoubleValue(), and the unit type matches TypeWithCalcResolved(), which is incorrect. This patch partially fixes the issue when the calc expression can be resolved without type conversion. Handling type conversion is more complicated and hence left broken by this patch (as it's already broken). Bug: 982542 Change-Id: I258b3d1aeec69fb65fbadd86981e97974239289b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696191 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#676452} -- wpt-commits: 14acac099af003b048229966651d558f508e2b9a wpt-pr: 17775
a1a37cb022177327225c26947564c61215226c00: Bug 1565357 [wpt PR 17781] - custom-elements: Fix 'capture' attribute existence check, a=testonly
Kent Tamura <tkent@chromium.org> - Mon, 22 Jul 2019 10:24:52 +0000 - rev 484305
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565357 [wpt PR 17781] - custom-elements: Fix 'capture' attribute existence check, a=testonly Automatic update from web-platform-tests custom-elements: Fix 'capture' attribute existence check in reactions/HTMLInputElement.html Do not call 'capture' property getter. -- wpt-commits: 40ef441b2f6ff803248bf71f03334b1326371c2b wpt-pr: 17781
3f420b25532cbc1cc2bb3b2b51430ec9c83b205b: Bug 1565350 [wpt PR 17778] - [css-transforms] Avoid using assert_own_property on testing style properties., a=testonly
Boris <boris.chiou@gmail.com> - Mon, 22 Jul 2019 10:24:47 +0000 - rev 484304
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565350 [wpt PR 17778] - [css-transforms] Avoid using assert_own_property on testing style properties., a=testonly Automatic update from web-platform-tests [css-transforms] Avoid using assert_own_property on style property. (#17778) These `assert_own_property` tests cause these CSS tests to fail on Firefox only, and I think these properties are not supposted to be own properties, so use a similar way as https://github.com/web-platform-tests/wpt/pull/16892, to test the existence of these properties. -- wpt-commits: 47543ee66eb535b6910292f199f3b789bec263f0 wpt-pr: 17778
6d25cef61f175cb7d5bd0b150ad8df755e1342c5: Bug 1565300 [wpt PR 17642] - Implement RTCPeerConnection.onicecandidateerror and add web-platform-test, a=testonly
Eldar Rello <elrello@microsoft.com> - Mon, 22 Jul 2019 10:24:42 +0000 - rev 484303
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565300 [wpt PR 17642] - Implement RTCPeerConnection.onicecandidateerror and add web-platform-test, a=testonly Automatic update from web-platform-tests Implement RTCPeerConnection.onicecandidateerror and add web-platform-test Spec: https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-onicecandidateerror Intent: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/fs-Y4awdYj0 Bug: webrtc:3098 Change-Id: I9c4a3ec75050e85f2a13b896f580bc16206ca2c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607800 Commit-Queue: Eldar Rello <elrello@microsoft.com> Reviewed-by: Qingsi Wang <qingsi@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#676359} -- wpt-commits: ee75c68c4ef501f914e62167d941cc046caec0ec wpt-pr: 17642
9ee6f1478c5e930401a07d823a53871dd94ca7ef: Bug 1565038 [wpt PR 17772] - Change height and width of set.py tests to be larger than min for chrome, a=testonly
julianrkung <julianrkung@berkeley.edu> - Mon, 22 Jul 2019 10:24:37 +0000 - rev 484302
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565038 [wpt PR 17772] - Change height and width of set.py tests to be larger than min for chrome, a=testonly Automatic update from web-platform-tests webdriver: make height and width of tests larger than min for chrome (#17772) -- wpt-commits: 36acf7a01cb8ffbbafbd578229c5ad3fde2e47cc wpt-pr: 17772
203009577895c8f10b04ecbbb3bd9c6081e4dbe0: Bug 1564592 [wpt PR 17736] - [UserTimingL3] Throw TypeError on negative time stamp, a=testonly
Liquan(Max) Gu <maxlg@chromium.org> - Mon, 22 Jul 2019 10:24:31 +0000 - rev 484301
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1564592 [wpt PR 17736] - [UserTimingL3] Throw TypeError on negative time stamp, a=testonly Automatic update from web-platform-tests [UserTimingL3] Throw TypeError on negative time stamp According to the spec (https://w3c.github.io/user-timing/): 1. "If markOptions's startTime is negative, throw a TypeError.", 2. "If mark is negative, throw a TypeError." when "Convert a mark to a timestamp" The CL is to add these two checks accordingly. Bug: 953865 Change-Id: I8475870cc883dc8c3d3d4f3e65a9d5a0a2189a58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691871 Reviewed-by: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/master@{#676266} -- wpt-commits: a819c8a4b2760a1547e63d57e39e3f34dbc5da41 wpt-pr: 17736
f34f72baed9a646aba32a2aac86c2aac1f6faed3: Bug 1565544 [wpt PR 17782] - [LayoutNG] Consider inline-level OOF-positioned nodes as "adjoining"., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Mon, 22 Jul 2019 10:24:26 +0000 - rev 484300
Push 113760 by james@hoppipolla.co.uk at Wed, 24 Jul 2019 12:52:31 +0000
Bug 1565544 [wpt PR 17782] - [LayoutNG] Consider inline-level OOF-positioned nodes as "adjoining"., a=testonly Automatic update from web-platform-tests [LayoutNG] Consider inline-level OOF-positioned nodes as "adjoining". "adjoining" objects are used to indicate that a particular node might need relayout once its BFC block-offset is resolved. Previously we thought that we just needed to know about "adjoining-floats". However inline-level OOF-positioned nodes also needs to know its BFC block-offset as the static-position of these nodes depend on where floats are. Previously as we didn't know that we needed to relayout these nodes we'd get the incorrect static-position. Now these nodes get the correct static-position. Bug: 982403, 980908 Change-Id: I89f18298fd7379358a681b98514891d8d35bc38e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1692627 Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#676263} -- wpt-commits: 4f954c15e1dc8cf94f7a2231f648fb640509d9d4 wpt-pr: 17782
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip