e1c49ed3584b7db1e6b3a45d0a2824cf9e56ca04: Bug 1530837 [wpt PR 15524] - Update README and META.yml to use the MathML Core spec., a=testonly
Frédéric Wang <fred.wang@free.fr> - Wed, 06 Mar 2019 12:35:56 +0000 - rev 464665
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1530837 [wpt PR 15524] - Update README and META.yml to use the MathML Core spec., a=testonly Automatic update from web-platform-tests Update README and META.yml to use the MathML Core spec. (#15524) Meta help still needs to be updated. -- wpt-commits: 1d89f3761c2a5b25dadf6dc4d868b0d6a8ea0bfc wpt-pr: 15524
70fc9e4d62ddac3e8a8e6c2356f1756b739d502c: Bug 1530834 [wpt PR 15522] - [Azure Pipelines] Put artifact name in urlencoded POST body, a=testonly
Philip Jägenstedt <philip@foolip.org> - Wed, 06 Mar 2019 12:35:54 +0000 - rev 464664
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1530834 [wpt PR 15522] - [Azure Pipelines] Put artifact name in urlencoded POST body, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Put artifact name in urlencoded POST body (#15522) ... instead of in the query string. This will probably resolve the "POST requests require a Content-length header" problem [1] assuming that the cause is a version of curl that doesn't send the header if the request has no body. [1] https://dev.azure.com/web-platform-tests/wpt/_build/results?buildId=7671 -- wpt-commits: 5803f5e36a2d8ff3d06e135f39803f9d282fb520 wpt-pr: 15522
df46e8c9bc569597d1774836fc8b16deb1a269ff: Bug 1530831 [wpt PR 15513] - Update |active_tree_scopes| etc when shadow root with adoptedStyleSheets is inserted, a=testonly
Rakina Zata Amni <rakina@chromium.org> - Wed, 06 Mar 2019 12:35:37 +0000 - rev 464663
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1530831 [wpt PR 15513] - Update |active_tree_scopes| etc when shadow root with adoptedStyleSheets is inserted, a=testonly Automatic update from web-platform-tests Update |active_tree_scopes| etc when shadow root with adoptedStyleSheets is inserted When a shadow root with non-empty |adoptedStyleSheets| is inserted, we should make sure that the |active_tree_scopes_| list is updated and the tree scope is marked dirty so that style invalidation & recalc will work. Bug: 934340 Change-Id: I365936e4bcc0132c938fe4e200e208abac91d3d9 Reviewed-on: https://chromium-review.googlesource.com/c/1482437 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#634624} -- wpt-commits: cf8e7d68a5fe9e40f6492706dbaafa01f8e8bfc9 wpt-pr: 15513
f80199c17ea799abafe2b9d73d0546367aabcb45: Bug 1529080 [wpt PR 15398] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 19 Feb 2019 20:34:40 +0000 - rev 464662
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529080 [wpt PR 15398] - Update wpt metadata, a=testonly wpt-pr: 15398 wpt-type: metadata
e1b3b233b7b817ab02f5a8b04c59e1bc0074ec1a: Bug 1529080 [wpt PR 15398] - Restrict Device{Orientation|Motion}Events to secure origins., a=testonly
Balazs Engedy <engedy@chromium.org> - Wed, 06 Mar 2019 12:35:23 +0000 - rev 464661
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529080 [wpt PR 15398] - Restrict Device{Orientation|Motion}Events to secure origins., a=testonly Automatic update from web-platform-tests Restrict Device{Orientation|Motion}Events to secure origins. Registering event handlers to `devicemotion`, `deviceorientation`, and `deviceorientationabsolute` events is still possible, but the handlers will never be invoked in non-secure browsing contexts. The following, related, interfaces are marked as [SecureContext]: -- DeviceOrientationEvent, -- DeviceMotionEvent, -- DeviceMotionEventAcceleration, -- DeviceMotionEventRotationRate. The change is gated on RestrictDeviceSensorEventsToSecureContexts, which is disabled by default, so this CL is a no-op unless the base::Feature with the same name is manually enabled. Intent to remove: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/5yqfAXibz1I Bug: 932078 Change-Id: I9baaafd1f4483f121feadc054650c4d510a2c88d TBR: haraken@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/1473992 Commit-Queue: Balazs Engedy <engedy@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#634620} -- wpt-commits: c401bb4fdb48c7536a96d25570242444f1b6b5f0 wpt-pr: 15398
9af8aa6f143fb5c83968e72355286ed39c0e080e: Bug 1530825 [wpt PR 15519] - [Azure Pipelines] POST to the /api/checks/azure/1234 endpoint, a=testonly
Philip Jägenstedt <philip@foolip.org> - Wed, 06 Mar 2019 12:35:21 +0000 - rev 464660
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1530825 [wpt PR 15519] - [Azure Pipelines] POST to the /api/checks/azure/1234 endpoint, a=testonly Automatic update from web-platform-tests [Azure Pipelines] POST to the /api/checks/azure/1234 endpoint (#15519) This regressed in https://github.com/web-platform-tests/wpt/pull/15384. -- wpt-commits: 8d7111a760e99de3e6fd87e0914c60df98836e38 wpt-pr: 15519
6efd7c8086b30f00184ada4207a5797c7ed26511: Bug 1526801 [wpt PR 15292] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 28 Feb 2019 13:00:32 +0000 - rev 464659
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1526801 [wpt PR 15292] - Update wpt metadata, a=testonly wpt-pr: 15292 wpt-type: metadata
325b153de47f8f7395434535bf434eb2dcff08da: Bug 1526801 [wpt PR 15292] - [PeerConnection] Fire signalingstatechange event at the right time, a=testonly
Guido Urdaneta <guidou@chromium.org> - Wed, 06 Mar 2019 12:35:06 +0000 - rev 464658
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1526801 [wpt PR 15292] - [PeerConnection] Fire signalingstatechange event at the right time, a=testonly Automatic update from web-platform-tests [PeerConnection] Fire signalingstatechange event at the right time Prior to this CL, the event was fired before the transceiver state was updated, in contradiction with the spec, which says it should be fired after the transceiver state is updated. Bug: 920200 Change-Id: I757cc0161a5da4888cd628619180e24a54dc732b Reviewed-on: https://chromium-review.googlesource.com/c/1458203 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#634609} -- wpt-commits: 0f4203743c56377734f9682abb015d56d6a1a71e wpt-pr: 15292
063b443f99cd6346bfaf3ac5f93f0c7019a27550: Bug 1528954 [wpt PR 15461] - HTML: opener of a Window sans browsing context, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Wed, 06 Mar 2019 12:35:03 +0000 - rev 464657
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1528954 [wpt PR 15461] - HTML: opener of a Window sans browsing context, a=testonly Automatic update from web-platform-tests HTML: opener of a Window sans browsing context For https://github.com/whatwg/html/pull/4379. -- wpt-commits: ad1ab06b7fcdbf7ef24cf0ed8aa13ac36d04272a wpt-pr: 15461
d3eedffa9545cd523e3632aac00c7336c056cbc6: Bug 1528949 [wpt PR 15460] - HTML: window.focus() sans browsing context, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Wed, 06 Mar 2019 12:35:01 +0000 - rev 464656
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1528949 [wpt PR 15460] - HTML: window.focus() sans browsing context, a=testonly Automatic update from web-platform-tests HTML: window.focus() sans browsing context For https://github.com/whatwg/html/pull/4377. -- wpt-commits: 84a44957233c13fb21f5d97b06db1d89076fb144 wpt-pr: 15460
9b7b2b7524d935e5a26ccd7a433146598a4eeb2e: Bug 1530812 [wpt PR 15495] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 28 Feb 2019 12:42:46 +0000 - rev 464655
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1530812 [wpt PR 15495] - Update wpt metadata, a=testonly wpt-pr: 15495 wpt-type: metadata
7e01f5fb1b40e32e61daabece9714c70a62c1661: Bug 1530812 [wpt PR 15495] - Add signed exchange reporting error test cases, a=testonly
Tsuyoshi Horo <horo@chromium.org> - Wed, 06 Mar 2019 12:34:45 +0000 - rev 464654
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1530812 [wpt PR 15495] - Add signed exchange reporting error test cases, a=testonly Automatic update from web-platform-tests Add signed exchange reporting error test cases Bug: 910516 Change-Id: I01f776e0a787e97430cc033d55bb1a32e900f9e9 Reviewed-on: https://chromium-review.googlesource.com/c/1480363 Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#634520} -- wpt-commits: a4d3950853b324eaeb4c49be58df1bed832519ca wpt-pr: 15495
11b9b53dc207b8a111f3f88a3450f32a165dab14: Bug 1529263 [wpt PR 15399] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 21 Feb 2019 01:25:03 +0000 - rev 464653
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529263 [wpt PR 15399] - Update wpt metadata, a=testonly wpt-pr: 15399 wpt-type: metadata
e225248e3398a84aeba120216e364e14d14b22fd: Bug 1529263 [wpt PR 15399] - Implement scroll-snap-stop: always, a=testonly
Sandra Sun <sunyunjia@chromium.org> - Wed, 06 Mar 2019 12:34:30 +0000 - rev 464652
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529263 [wpt PR 15399] - Implement scroll-snap-stop: always, a=testonly Automatic update from web-platform-tests Implement scroll-snap-stop: always As specified in the spec, when the snap-area has scroll-snap-stop: always, we should not pass its snap position when scrolling with an intended direction. This patch implements this feature by adding another round of search for the IntendedEndAndDirectionStrategy. This second round searches for the snap position with scroll-snap-stop: always that's closest to the scroll's start position. It then compares with the result from the first round of search, which is the snap position closest to the scroll's target position. The comparison selects the area closest to the scroll's start position ensuring a an area with snap stop is never bypassed. Bug: 823998 Change-Id: Ic40f82263ced85f8a72c8f5a82d4fb76e403398f Reviewed-on: https://chromium-review.googlesource.com/c/1460875 Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Sandra Sun <sunyunjia@chromium.org> Cr-Commit-Position: refs/heads/master@{#634421} -- wpt-commits: 181f8381fe9373e027f4b5ba5d1439843ad2c2e6 wpt-pr: 15399
8b69d51eaae559880834e12b2dceba7d9f055b79: Bug 1529208 [wpt PR 15469] - [Code Health] Fix incorrect test name, a=testonly
Yi Gu <yigu@chromium.org> - Wed, 06 Mar 2019 12:34:28 +0000 - rev 464651
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529208 [wpt PR 15469] - [Code Health] Fix incorrect test name, a=testonly Automatic update from web-platform-tests [Code Health] Fix incorrect test name wpt/web-animations/timing-model/animations/set-the-animation-start-time.html was renamed in [1] but the name change was not reflected elsewhere. In addition, the expectation file for the test on Android seems unnecessary. [1] https://chromium.googlesource.com/chromium/src/+/bf6c3b061813db88ca12c59690cece60d0b672f7 Change-Id: I6a640c3d56203380ad19ca3b1bb1278cc6971bd8 Reviewed-on: https://chromium-review.googlesource.com/c/1477938 Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#634404} -- wpt-commits: b055c7c24f26f1f61c11bb1efcdbcec5805f5f47 wpt-pr: 15469
1966a78128ba364656ebe9aee80f7f5a1b63e90b: Bug 1529821 [wpt PR 15506] - Surface dtlsTransport via state-surfacer, a=testonly
Harald Alvestrand <hta@chromium.org> - Wed, 06 Mar 2019 12:34:26 +0000 - rev 464650
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529821 [wpt PR 15506] - Surface dtlsTransport via state-surfacer, a=testonly Automatic update from web-platform-tests Surface dtlsTransport via state-surfacer This allows for more consistent state information. Bug: chromium:907849 Change-Id: I8b71b3ec3eb1acf83624969190519c5f18b2a19e Reviewed-on: https://chromium-review.googlesource.com/c/1455896 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#633958} -- wpt-commits: 36baff5e6981e5a235ed1c5f13b45ffed241770b wpt-pr: 15506
c2de5b0649719b063e0c85d084c37b99db7cc11b: Bug 1529459 [wpt PR 15179] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 25 Feb 2019 14:06:04 +0000 - rev 464649
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529459 [wpt PR 15179] - Update wpt metadata, a=testonly wpt-pr: 15179 wpt-type: metadata
496fc0a8cd1d53d2066ecf4ccadf557261dc935b: Bug 1529459 [wpt PR 15179] - Add tentative WPT to verify download in sandbox, a=testonly
Yao Xiao <yaoxia@chromium.org> - Wed, 06 Mar 2019 12:34:11 +0000 - rev 464648
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529459 [wpt PR 15179] - Add tentative WPT to verify download in sandbox, a=testonly Automatic update from web-platform-tests Add tentative WPT to verify download in sandbox General testing idea: For a network request, the server stores a token in stash. And after a fixed period of time, we validate the token in the stash to verify a download has happened. Also assert that no additional navigation should happen. In the case of <a download> where the decision of download can be made before resource fetching, the server sets the token immediately. In the case of navigation to a download, the server will stream a response over 1 seconds and set the token at the end only when the socket has been connected. So it is able to detect any download cancellation while fetching the resource. Bug: 539938, 927183 Change-Id: I7b90d46504603f60938a46acee9fbd7d1483988b Reviewed-on: https://chromium-review.googlesource.com/c/1446395 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/master@{#634249} -- wpt-commits: 245334dcc1695c3dbc4e1fcdbe849224234093fc wpt-pr: 15179
cd9ac71c85c6abbea6f856c576a3c261c34e6fba: Bug 1529818 [wpt PR 15492] - LongTasks: fix sibling layout test, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Wed, 06 Mar 2019 12:34:08 +0000 - rev 464647
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529818 [wpt PR 15492] - LongTasks: fix sibling layout test, a=testonly Automatic update from web-platform-tests LongTasks: fix sibling layout test This CL allows the main frame to produce a long task that is observed by the child frame. Such a long task can be detected because the attribution will be same-origin-ancestor. Bug: 927866 Change-Id: I38849b5f44172cbffd25f3ab429b0c1a96b0f1e3 Reviewed-on: https://chromium-review.googlesource.com/c/1480114 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#634243} -- wpt-commits: 493fdc7e7908360273baa0ee13421fff692cf8ed wpt-pr: 15492
3df4d4a707f5ae145cf2249818b7ce1e3021e939: Bug 1529814 [wpt PR 15502] - [Azure Pipelines] Allow Safari TP to be manually triggered, a=testonly
Philip Jägenstedt <philip@foolip.org> - Wed, 06 Mar 2019 12:34:06 +0000 - rev 464646
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1529814 [wpt PR 15502] - [Azure Pipelines] Allow Safari TP to be manually triggered, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Allow Safari TP to be manually triggered (#15502) To help alleviate https://github.com/web-platform-tests/wpt/issues/15500. -- wpt-commits: bbb94679c4f6ca8d6779631eacb2871dd804a70a wpt-pr: 15502
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip