aa5c03387a3febb2fc912a8a420d2e54d43a1796: Bug 1599576 [wpt PR 20461] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 03 Dec 2019 17:15:33 +0000 - rev 568188
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1599576 [wpt PR 20461] - Update wpt metadata, a=testonly wpt-pr: 20461 wpt-type: metadata
5aa0cb11f7c930c308ae499198e3895fb38529a9: Bug 1599576 [wpt PR 20461] - Add `Set Permission` API to testdriver.js, a=testonly
Luke Zielinski <44509484+LukeZielinski@users.noreply.github.com> - Thu, 05 Dec 2019 15:47:19 +0000 - rev 568187
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1599576 [wpt PR 20461] - Add `Set Permission` API to testdriver.js, a=testonly Automatic update from web-platform-tests Add `Set Permission` API to testdriver.js (#20461) -- wpt-commits: 302caa87f6d4dc21bbf899c5177ca238357b91d3 wpt-pr: 20461
54a100e46e839db076a17ab5d6cdf501cf666c0e: Bug 1600689 [wpt PR 20562] - Add a test for jobs scheduled on an epochs push, a=testonly
jgraham <james@hoppipolla.co.uk> - Thu, 05 Dec 2019 15:47:14 +0000 - rev 568186
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600689 [wpt PR 20562] - Add a test for jobs scheduled on an epochs push, a=testonly Automatic update from web-platform-tests Add a test for jobs scheduled on an epochs push (#20562) -- wpt-commits: b40982a56aab1cff622399375c8a513be3dfcd4a wpt-pr: 20562
dc6c230930c75cfb4f719d1b773ce3fe0c1e8d53: Bug 1600676 [wpt PR 20560] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 03 Dec 2019 11:10:06 +0000 - rev 568185
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600676 [wpt PR 20560] - Update wpt metadata, a=testonly wpt-pr: 20560 wpt-type: metadata
f3bb93a352cb7831df3ca5613a33db97fb45bfb6: Bug 1600676 [wpt PR 20560] - Fix WPT test: content-security-policy/reporting/report-only-unsafe-eval.html, a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Thu, 05 Dec 2019 15:47:06 +0000 - rev 568184
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600676 [wpt PR 20560] - Fix WPT test: content-security-policy/reporting/report-only-unsafe-eval.html, a=testonly Automatic update from web-platform-tests Fix WPT test: content-security-policy/reporting/report-only-unsafe-eval.html This test doesn't pass, because there is a problem with Chrome's implementation (See https://crbug.com/980127) and because there are two problems in the test itself. 1) t_spv.done() is never called. 2) A typing mistake in "tsv_unreached_func" Bug: 980127 Change-Id: I91949f64db3f3d7d3033d559d8e277b2cb980b13 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946482 Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#720890} -- wpt-commits: 54b0b7b15ec1f26b64c13a54b832b29456f569bd wpt-pr: 20560
58e46382190a059c31a5c39411bff1265ccc0534: Bug 1600810 [wpt PR 20568] - [css-pseudo] Set default styles to ::marker, a=testonly
Oriol Brufau <obrufau@igalia.com> - Thu, 05 Dec 2019 15:47:00 +0000 - rev 568183
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600810 [wpt PR 20568] - [css-pseudo] Set default styles to ::marker, a=testonly Automatic update from web-platform-tests [css-pseudo] Set default styles to ::marker Markers should have the following styles by default: - unicode-bidi: isolate - font-variant-numeric: tabular-nums Spec: https://drafts.csswg.org/css-pseudo-4/#marker-pseudo Bug: 457718 TEST=external/wpt/css/css-pseudo/marker-default-styles.html TEST=external/wpt/css/css-pseudo/marker-font-variant-numeric-default.html TEST=external/wpt/css/css-pseudo/marker-font-variant-numeric-normal.html TEST=external/wpt/css/css-pseudo/marker-unicode-bidi-default.html TEST=external/wpt/css/css-pseudo/marker-unicode-bidi-normal.html The unicode-bidi tests fail in legacy because of bug 1012289. And marker-font-variant-numeric-normal.html fails everywhere because nested ::marker pseudo-elements are not supported yet. Change-Id: I80360d0e2bfa78ebca1c10e1064daa17e66e6f22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943228 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#720875} -- wpt-commits: be856ef52c77169447017256bb81adf058e67880 wpt-pr: 20568
fb6bea35cfd6ca885c7af81be849927c5a6f5152: Bug 1600349 [wpt PR 20535] - Add META.yml for fetch metadata, a=testonly
Simon Pieters <zcorpan@gmail.com> - Thu, 05 Dec 2019 15:46:55 +0000 - rev 568182
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600349 [wpt PR 20535] - Add META.yml for fetch metadata, a=testonly Automatic update from web-platform-tests Add META.yml for fetch metadata (#20535) -- wpt-commits: 0317e9a8591851f97d59c9de28c46ea1c2a25f88 wpt-pr: 20535
951eb77e57841f5f1212ca0c2b15368ab76e4cf8: Bug 1600611 [wpt PR 20555] - Verify that nested frames can navigate same-origin ancestors., a=testonly
Mike West <mkwst@chromium.org> - Thu, 05 Dec 2019 15:46:50 +0000 - rev 568181
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600611 [wpt PR 20555] - Verify that nested frames can navigate same-origin ancestors., a=testonly Automatic update from web-platform-tests Verify that nested frames can navigate same-origin ancestors. Bug: 1027148 Change-Id: I6630788dad82d6b98f2630d7deb3cf64dccfd652 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944859 Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#720844} -- wpt-commits: f5350219acc9293323b87811bc9fabad6300193e wpt-pr: 20555
84a97b774d4b8cbcd1c9ea0e1d5bc43a0e811d8b: Bug 1600241 [wpt PR 20527] - [webnfc] Do not use 'any' to define NDEFRecordInit#data, a=testonly
Leon Han <leon.han@intel.com> - Thu, 05 Dec 2019 15:46:45 +0000 - rev 568180
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600241 [wpt PR 20527] - [webnfc] Do not use 'any' to define NDEFRecordInit#data, a=testonly Automatic update from web-platform-tests [webnfc] Do not use 'any' to define NDEFRecordInit#data Use the following union type instead of 'any' to define NDEFRecordInit#data. " typedef (DOMString or BufferSource or NDEFMessageInit) NDEFRecordDataSource " The spec change: https://github.com/w3c/web-nfc/pull/454 BUG=520391 Change-Id: Ic917be001d5e3502caeea29ff4a3401ff7197298 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941083 Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Leon Han <leon.han@intel.com> Cr-Commit-Position: refs/heads/master@{#720803} -- wpt-commits: 0ac244337ec64d16f50eb9fe8202413e76ec58c1 wpt-pr: 20527
897cd6d1fe30db13980b43dc2932f139ce8057f0: Bug 1598549 [wpt PR 20391] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 03 Dec 2019 04:57:57 +0000 - rev 568179
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1598549 [wpt PR 20391] - Update wpt metadata, a=testonly wpt-pr: 20391 wpt-type: metadata
014ed6bd538dec3df1db611a662cffbda8966741: Bug 1598549 [wpt PR 20391] - [webnfc] Introduce NDEFRecordInit#id to support writing record id, a=testonly
Leon Han <leon.han@intel.com> - Thu, 05 Dec 2019 15:46:29 +0000 - rev 568178
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1598549 [wpt PR 20391] - [webnfc] Introduce NDEFRecordInit#id to support writing record id, a=testonly Automatic update from web-platform-tests [webnfc] Introduce NDEFRecordInit#id to support writing record id The plan is: 1. Introduces NDEFRecord{Init}#id and supports reading. Already done by crrev.com/c/1861574. 2. Supports writing. This CL is focused on impl in Blink, with the following CLs focused on impl in Device Service. crrev.com/c/1910906 crrev.com/c/1911385 crrev.com/c/1915940 crrev.com/c/1916261 3. Introduces NFCScanOptions#id and filters records by it when scanning. 4. Removes NDEFMessage{Init}#url and old impl of the author record. The spec changes: https://github.com/w3c/web-nfc/pull/338 https://github.com/w3c/web-nfc/pull/340 https://github.com/w3c/web-nfc/pull/446 BUG=520391 Change-Id: Ie6f5b2978f78676c3aa607d09e7ffd5bbb5005d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928891 Reviewed-by: François Beaufort <beaufort.francois@gmail.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Leon Han <leon.han@intel.com> Cr-Commit-Position: refs/heads/master@{#720792} -- wpt-commits: d9ee4f3e4ef4792b085687584981611e0b74f003 wpt-pr: 20391
1252da20333aa5a1ce410f87af608a33f76306c9: Bug 1599802 [wpt PR 20482] - Always update intervals using the "latest update time", a=testonly
Fredrik Söderquist <fs@opera.com> - Thu, 05 Dec 2019 15:46:24 +0000 - rev 568177
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1599802 [wpt PR 20482] - Always update intervals using the "latest update time", a=testonly Automatic update from web-platform-tests Always update intervals using the "latest update time" For interval updates performed "outside" of the regular flow in SMILTimeContainer, we would use the "previous" presentation - i.e the time just before the time we latest updated timing to. This could cause elements to resolve intervals in the past - for example when the latest update time was at the end of an interval it could discard the current interval and resolve an interval in the past, which could then be propagated to its dependents. When these elements were later updated by the main update loop they would again discard the current (in the past) interval and resolve a new one, notifying its dependents. Repeat. Instead always use the "latest update time" (the same is used by SMILTimeContainer::UpdateIntervals) as the argument to Updateinterval(), and only use the "previous" presentation time when checking if the active state may have changed in a relevant way and for rescheduling. Bug: 1021630, 1028839, 1029327 Change-Id: Ibe691ae336df51a36626fdd800e5ddc2303aee5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1939788 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#720669} -- wpt-commits: 28b096731f4582bda6491400941cf0a7f645b45f wpt-pr: 20482
fdc43bf13d102c0850e5f42e755166983e611a1a: Bug 1600420 [wpt PR 20544] - Update mypy to 0.750, a=testonly
pyup-bot <github-bot@pyup.io> - Thu, 05 Dec 2019 15:46:18 +0000 - rev 568176
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600420 [wpt PR 20544] - Update mypy to 0.750, a=testonly Automatic update from web-platform-tests Update mypy from 0.740 to 0.750 -- wpt-commits: 923cb3c2e315d6bf945254bf2f751d20718d9922 wpt-pr: 20544
a6b5827b6d384cb40a3f149ca99f2f3ee92156c7: Bug 1600703 [wpt PR 20564] - Add Chrome expectations to multiTouchPointsWithPause.html.ini, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Thu, 05 Dec 2019 15:46:13 +0000 - rev 568175
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600703 [wpt PR 20564] - Add Chrome expectations to multiTouchPointsWithPause.html.ini, a=testonly Automatic update from web-platform-tests Add Chrome expectations to multiTouchPointsWithPause.html.ini (#20564) -- wpt-commits: c76f777b0480189e22c3b79e188200a946c45045 wpt-pr: 20564
642b105d778c3072b77d4bbb6594feb613c96666: Bug 1600682 [wpt PR 20561] - Fix email handing for decision task, a=testonly
jgraham <james@hoppipolla.co.uk> - Thu, 05 Dec 2019 15:46:08 +0000 - rev 568174
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600682 [wpt PR 20561] - Fix email handing for decision task, a=testonly Automatic update from web-platform-tests Fix email handing for decision task (#20561) * Null check the pusher - This can be null for GitHub actions * Ensure decision task always has a valid email -- wpt-commits: f2656321731150c765a52fd2e1443eae339e5530 wpt-pr: 20561
700a7a8a5c0fce66157b4830d8471163a3a0c493: Bug 1600587 [wpt PR 20553] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 02 Dec 2019 23:16:29 +0000 - rev 568173
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600587 [wpt PR 20553] - Update wpt metadata, a=testonly wpt-pr: 20553 wpt-type: metadata
65aba49e0ee4baedf8748b815aedcc9f6a014de3: Bug 1600587 [wpt PR 20553] - CSS images to respect Content-DPR, a=testonly
Yoav Weiss <yoavweiss@chromium.org> - Thu, 05 Dec 2019 15:46:00 +0000 - rev 568172
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600587 [wpt PR 20553] - CSS images to respect Content-DPR, a=testonly Automatic update from web-platform-tests CSS images to respect Content-DPR CSS images should take Content-DPR into account when calculating their intrinsic dimensions. They currently don't. This CL fixes that. Bug: 1029313 Change-Id: Iafb2e5d88c1a0bbf0a13b00ddb46ad643f38c8d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944496 Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#720531} -- wpt-commits: aae310c2a9c3adb77659cb313f975ccfb6ff9c67 wpt-pr: 20553
a601797af709ac1360280789010bbc258cb8ec01: Bug 1600107 [wpt PR 20510] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 02 Dec 2019 23:09:54 +0000 - rev 568171
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600107 [wpt PR 20510] - Update wpt metadata, a=testonly wpt-pr: 20510 wpt-type: metadata
2272c1fc7ead038011fad288fdf9d0793739ed60: Bug 1600107 [wpt PR 20510] - [Longtasks] Add test for buffered flag, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Thu, 05 Dec 2019 15:45:51 +0000 - rev 568170
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600107 [wpt PR 20510] - [Longtasks] Add test for buffered flag, a=testonly Automatic update from web-platform-tests [Longtasks] Add test for buffered flag (#20510) Bug: 1016815 Change-Id: I6c3ab2e1551de2bea9eaacd211c976bf64da66bc -- wpt-commits: 2bbd506a655a6b94d57d5b84f211f9ccaca89131 wpt-pr: 20510
8c41b12db448b92d39fb42c11e2fa903a3991341: Bug 1600383 [wpt PR 20542] - Don't set taskcluster variables when we don't want to run the task, a=testonly
jgraham <james@hoppipolla.co.uk> - Thu, 05 Dec 2019 15:45:46 +0000 - rev 568169
Push 12493 by ffxbld-merge at Mon, 06 Jan 2020 15:38:57 +0000
Bug 1600383 [wpt PR 20542] - Don't set taskcluster variables when we don't want to run the task, a=testonly Automatic update from web-platform-tests Don't set taskcluster variables when we don't want to run the task (#20542) Previously we had a single let block setting all the variables for the .taskcluster.yml file. But this was evaluated even on events for which we don't run tasks. That caused bogus failures because the logic didn't account for all the possible event types. Instead only evaluate the variables used in the task definition in a block guarded by "if run_task". -- wpt-commits: cf170f5c423b3ce2312e997afcb06ba1f3fc641e wpt-pr: 20542
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip