1e2d46a027aac806dc2d95b2827b2ba44f4f3909: Bug 1591482 [wpt PR 19894] - Update mozprofile to 2.4.0, a=testonly
pyup-bot <github-bot@pyup.io> - Mon, 04 Nov 2019 11:06:31 +0000 - rev 564689
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1591482 [wpt PR 19894] - Update mozprofile to 2.4.0, a=testonly Automatic update from web-platform-tests Update mozprofile from 2.3.0 to 2.4.0 -- wpt-commits: 013b8e6ce3f6f098d1246690c380a69160e33636 wpt-pr: 19894 Differential Revision: https://phabricator.services.mozilla.com/D53479
e7ca863c9920b3a28657815d351e84973f59d2c8: Bug 1588815 [wpt PR 19703] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 25 Oct 2019 17:04:41 +0000 - rev 564688
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1588815 [wpt PR 19703] - Update wpt metadata, a=testonly wpt-pr: 19703 wpt-type: metadata Differential Revision: https://phabricator.services.mozilla.com/D53478
882f13426698c48ef98024c93a1a230427535bd0: Bug 1588815 [wpt PR 19703] - Fetch Metadata: deprecate `nested-navigate` mode., a=testonly
Yifan Luo <lyf@google.com> - Mon, 04 Nov 2019 10:47:29 +0000 - rev 564687
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1588815 [wpt PR 19703] - Fetch Metadata: deprecate `nested-navigate` mode., a=testonly Automatic update from web-platform-tests Fetch Metadata: deprecate `nested-navigate` mode. As discussed in https://github.com/w3c/webappsec-fetch-metadata/issues/45, We have decided to shift the model around nested navigations from exposure via the request's `mode` to its `destination`. This patch shift the `nested-navigate` mode to two parts: - `navigate` for frame and iframe. - `no-cors` for object. Change-Id: I09a2be6b41547f6eeb1e308416234a40f0c9b5b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862690 Commit-Queue: Yifan Luo <lyf@google.com> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#709478} -- wpt-commits: 2eebdd2f37758cdd94c0c2bddc70763862ef283f wpt-pr: 19703 Differential Revision: https://phabricator.services.mozilla.com/D53477
e3527f492a980eacc6e66c5198c30e47e0a30ae4: Bug 1590620 [wpt PR 19841] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 02 Nov 2019 23:53:47 +0000 - rev 564686
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1590620 [wpt PR 19841] - Update wpt metadata, a=testonly wpt-pr: 19841 wpt-type: metadata Differential Revision: https://phabricator.services.mozilla.com/D53476
1edba25d9cb189a7b9c6cddf7c09615c27a1a05a: Bug 1590620 [wpt PR 19841] - Refactor MediaQueryList tests, a=testonly
Alexey Shvayka <shvaikalesh@gmail.com> - Mon, 04 Nov 2019 10:47:21 +0000 - rev 564685
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1590620 [wpt PR 19841] - Refactor MediaQueryList tests, a=testonly Automatic update from web-platform-tests Refactor MediaQueryList tests Fixes #19688 via bdbff2f. Fixes #14429. Follow-up of #18390. Related: #18389. * Add "width" and "height" paramters to `createIFrame` harness * Reflow <iframe> document in `createIFrame` * Introduce higher-level `createMQL` harness * Make `triggerMQLEvent` work with MediaQueryList * Use `createMQL` in "handleEvent" tests * Use `promise_rejects_*` and `EventWatcher` in "handleEvent" tests * Split "matchMedia.xht" and use new harness * Merge in "matchMediaAddListener.html" and use new harness * Rename "handleEvent" test * Merge in empty string test * Merge in "(min-width: 1px)" test * Add "use strict" directive * Remove bogus test * Remove extra MediaQueryList IDL tests * Remove extra MediaQueryListEvent IDL tests -- wpt-commits: 93d54359245275eac0045011572cfb87c65b8009 wpt-pr: 19841 Differential Revision: https://phabricator.services.mozilla.com/D53475
6aad4d54732be33af88d8106fe473a5044649246: Bug 1589280 [wpt PR 19746] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 02 Nov 2019 23:44:41 +0000 - rev 564684
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1589280 [wpt PR 19746] - Update wpt metadata, a=testonly wpt-pr: 19746 wpt-type: metadata Differential Revision: https://phabricator.services.mozilla.com/D53474
5b76b6ad6e917803448d63054d2cf2d2ecc8cd52: Bug 1589280 [wpt PR 19746] - Pass outside fetch client settings object for ServiceWorkerContainer#register(), a=testonly
Kenichi Ishibashi <bashi@chromium.org> - Mon, 04 Nov 2019 10:47:14 +0000 - rev 564683
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1589280 [wpt PR 19746] - Pass outside fetch client settings object for ServiceWorkerContainer#register(), a=testonly Automatic update from web-platform-tests Pass outside fetch client settings object for ServiceWorkerContainer#register() A brief summary of this plumbing is below: blink::ServiceWorkerContainer::registerServiceWorker() -> (IPC from a renderer to the browser) -> content::ServiceworkerContextCore::RegisterServiceWorker() Start a registration job asynchronously Create a ServiceWorkerVersion and set the passed settings object -> content::ServiceWorkerVersion::StartWorker() -> (IPC from the browser to a renderer) -> WebEmbeddedWorkerImpl::StartWorkerContext() -> ServiceWorkerGlobalScope::FetchAndRunClassicScript() (Note that renderer processes of above don't have to be the same.) This CL has behavioral changes. The 'Referer' header of the request triggered by register() in a document will be changed. Before this CL it was the url of the top-level script but after this CL it is document's url. This behavior is consistent with the spec. Bug: 937177 Change-Id: I4c137d10b7d5204151ae7eff8bfd8fdeb34fb365 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1861294 Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#709462} -- wpt-commits: 98f4cb23e0c4e16c821721601f1c94c837803ee8 wpt-pr: 19746 Differential Revision: https://phabricator.services.mozilla.com/D53473
5739670f837273840afe9307327a864a2b63d210: Bug 1591429 [wpt PR 19888] - Correct a path in update-built-tests.sh and run the update_built job more often., a=testonly
Ms2ger <Ms2ger@gmail.com> - Mon, 04 Nov 2019 10:47:09 +0000 - rev 564682
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1591429 [wpt PR 19888] - Correct a path in update-built-tests.sh and run the update_built job more often., a=testonly Automatic update from web-platform-tests Correct a path in update-built-tests.sh. This was added in #16816, but the test job wasn't run. -- Make sure the update_built job runs when it needs to. -- wpt-commits: 411c92baf1b714b3c970a8f3ed7575b6eddf63e9, 715bbdcf499287feaef607a7dc781a0a9115dfac wpt-pr: 19888 Differential Revision: https://phabricator.services.mozilla.com/D53472
a8ee22dc0997ef9ede0b163d9fd833ed3593e426: Bug 1591382 [wpt PR 19882] - [Azure Pipelines] switch from `--log-tbpl` to `--log-mach`, a=testonly
Philip Jägenstedt <philip@foolip.org> - Mon, 04 Nov 2019 10:47:04 +0000 - rev 564681
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1591382 [wpt PR 19882] - [Azure Pipelines] switch from `--log-tbpl` to `--log-mach`, a=testonly Automatic update from web-platform-tests [Azure Pipelines] switch from `--log-tbpl` to `--log-mach` (#19882) Like https://github.com/web-platform-tests/wpt/pull/19814. -- wpt-commits: 813f1404b6446912dbd5f7dd1794fbdc9391c8b5 wpt-pr: 19882 Differential Revision: https://phabricator.services.mozilla.com/D53471
a6d13f32c1b038171172834ba74c8b999ec025b8: Bug 1590229 [wpt PR 19814] - taskcluster: Use the mach logger instead of tbpl for stdout logging, a=testonly
Carlos Alberto Lopez Perez <clopez@igalia.com> - Mon, 04 Nov 2019 10:46:53 +0000 - rev 564680
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1590229 [wpt PR 19814] - taskcluster: Use the mach logger instead of tbpl for stdout logging, a=testonly Automatic update from web-platform-tests taskcluster: Use the mach logger instead of tbpl for stdout logging. (#19814) * With the mach logger a timestamp of when a test starts or ends is printed, which is very useful to detect tests taking too much time to complete or hanging. * On top of that the mach logger provides a more useful summary at the end of the suite run because it gives information about how many tests (and not only subtests) failed, also it summarizes the cause of the unexpected results (like error or timeout). * Also, the logs produces by the mach logger are more compact, around half the size in megabytes is needed for storing a log with match (instead of tbpl) * The environment variable TERM=dumb is passed to disable colors to be printed on the terminal -- wpt-commits: 8e9016586f4563dfcb4090882177e3c10866abe7 wpt-pr: 19814 Differential Revision: https://phabricator.services.mozilla.com/D53470
154a7e140b2f9075eb3a20a2a3fe6ccd6dd00a7d: Bug 1579753 [wpt PR 18921] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 25 Oct 2019 10:49:23 +0000 - rev 564679
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1579753 [wpt PR 18921] - Update wpt metadata, a=testonly wpt-pr: 18921 wpt-type: metadata Differential Revision: https://phabricator.services.mozilla.com/D53469
440468a2fa921a5c1525e5ab8a5b0799f40ecc52: Bug 1579753 [wpt PR 18921] - [NativeFileSystem] Make FileSystemHandle cloneable, a=testonly
Steve Becker <stevebe@microsoft.com> - Mon, 04 Nov 2019 10:46:45 +0000 - rev 564678
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1579753 [wpt PR 18921] - [NativeFileSystem] Make FileSystemHandle cloneable, a=testonly Automatic update from web-platform-tests [NativeFileSystem] Make FileSystemHandle cloneable Updates postMessage() to clone FileSystemFileHandle and FileSystemDirectoryHandle objects for same origin targets. Including a FileSystemHandle object with a cross origin message fails by dispatching a 'messageerror' event instead of 'message' event. The change consists of four parts: (1) Updates V8ScriptValueSerializerForModules to serialize FileSystemFileHandle and FileSystemDirectoryHandle into blink::SerializedScriptValue, by following these steps: * Write a tag for the handle type (file or directory). * Write the name of the file or directory. * Creates a mojom::blink::NativeFileSystemTransferTokenPtr by calling blink:NativeFileSystemHandle::Transfer(). This token informs the storage::NativeFileSystemManagerImpl that a transfer is in progress. The NativeFileSystemManagerImpl creates a NativeFileSystemTransferTokenImpl to store the information required to clone the handle. * Stores the token in blink::SerializedScriptValue::native_file_system_tokens_. This array tracks all cloned FileSystemFileHandle. The blink::mojom::CloneableMessage struct is also updated to hold this array for MessagePort and BroadcastChannels. * Write the index of the token in the native_file_system_tokens_ array. (2) Updates V8ScriptValueDeserializerForModules to deserialize FileSystemFileHandle objects when creating clones for the message targets. This is the inverse of (1). Deserializing uses mojom::blink::NativeFileSystemManager to redeem the token, which creates the mojom::blink::NativeFileSystemFileHandlePtr or mojom::blink::NativeFileSystemDirectoryHandlePtr using the info stored by NativeFileSystemTransferTokenImpl. (3) Updates content::NativeFileSystemManagerImpl to support token transfers. To redeem a token, NativeFileSystemManagerImpl receives a mojo message that includes the token as well as a request for a handle interface like mojom::blink::NativeFileSystemFileHandlePtr. NativeFileSystemManagerImpl finds the token and then binds the request. Token redemption does not return any results. Token redemption should never fail, unless a render process is misbehaving. NativeFileSystemManagerImpl performs a few sanity checks before binding the mojo request, including a token existence check, a handle type check and an origin check. If any of the sanity checks fail, NativeFileSystemManagerImpl silently fails closing the redeemed FileHandle's pipe. (4) Adds a cross origin check to window and message port messaging. Most message targets, like dedicated workers, are same origin only. However, both windows and message port messages can go cross origin. When a cross origin message includes a FileSystemHandle, the message must fail with a 'messageerror' event to prevent cross origin access to the FileSystemHandle. Messaging between windows already included origin information before this change. This change adds a NativeFileSystem origin check before dispatching a message event to a window. The message event is replaced with a message error when a cross origin NativeFileSystem object exists in the message data. For message ports, no sender origin information existed before this change. This change updates the CloneableMessage structs to include a 'sender_origin' url::Origin property. Message ports use this property to perform the same cross origin NativeFileSystem check as the window. The NativeFileSystemManagerImpl performs an additional origin check before binding the FileSystemHandle mojo request. The NativeFileSystemManagerImpl cannot trust the postMessage() origin check performed in the render process. Bug: 955192 Change-Id: Ieeb76bd8102067d70c5d7719622ecd4930c3a88f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1791942 Commit-Queue: Steve Becker <stevebe@microsoft.com> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by: Olivier Yiptong <oyiptong@chromium.org> Cr-Commit-Position: refs/heads/master@{#709407} -- wpt-commits: 474923949524b5c05a9e6f28ec082fdca87078de wpt-pr: 18921 Differential Revision: https://phabricator.services.mozilla.com/D53468
77dde54676247405ef3e5c7a76c44adc6b14d320: Bug 1591441 [wpt PR 19868] - [css-lists] Add test for list-style-type:<string> with Ahem font, a=testonly
Oriol Brufau <obrufau@igalia.com> - Mon, 04 Nov 2019 10:46:40 +0000 - rev 564677
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1591441 [wpt PR 19868] - [css-lists] Add test for list-style-type:<string> with Ahem font, a=testonly Automatic update from web-platform-tests [css-lists] Add test for list-style-type:<string> with Ahem font In the other reftests the width of the marker text is not known, so the references have to rely on some tricks with the ::before pseudo-element. This patch adds a test that uses the Ahem font, so that the width of the characters is known. Then the result can be checked with a simpler reference file. Note it fails in LayoutNG due to the lack of scrollbar (bug 1012294), but it passes in legacy. Bug: 687946 Change-Id: I7fd0856e93d4e489af65b5c767ec81c109804c5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1879067 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#709405} -- wpt-commits: 52aeca2db20bd3304407bf1a1fca4e5a827db243 wpt-pr: 19868 Differential Revision: https://phabricator.services.mozilla.com/D53467
fd3b805ec47687ab5f7138f2b10a327b84fdea5d: Bug 1591439 [wpt PR 19877] - [Azure Pipelines] increase experimental runs to every 3h, a=testonly
Philip Jägenstedt <philip@foolip.org> - Mon, 04 Nov 2019 10:46:35 +0000 - rev 564676
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1591439 [wpt PR 19877] - [Azure Pipelines] increase experimental runs to every 3h, a=testonly Automatic update from web-platform-tests [Azure Pipelines] increase experimental runs to every 3h (#19877) This uses the new epochs/three_hourly branch just introduced: https://github.com/web-platform-tests/wpt/pull/19873 The first run of the action created the branch: https://github.com/web-platform-tests/wpt/runs/274428602 Also decreate the job timeout to 3h to prevent a queue of jobs from building up if jobs start hanging or taking very long. The typical running time for both Edge and Safari are now ~1.7h. -- wpt-commits: 4efaeb295baf76c416c3c32ecf8d81d6c602ad11 wpt-pr: 19877 Differential Revision: https://phabricator.services.mozilla.com/D53466
58895d0e26661c16e61309a33f03fb49d3a56cbe: Bug 1591437 [wpt PR 19873] - [infra] add a cron workflow to update a new epochs/three_hourly branch, a=testonly
Philip Jägenstedt <philip@foolip.org> - Mon, 04 Nov 2019 10:46:30 +0000 - rev 564675
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1591437 [wpt PR 19873] - [infra] add a cron workflow to update a new epochs/three_hourly branch, a=testonly Automatic update from web-platform-tests [infra] add a cron workflow to update a new epochs/three_hourly branch (#19873) The epochs/three_hourly branch doesn't exist yet and nothing will be triggered by it initially, which makes it a good candidate for verifying that `./wpt rev-list` combined with GitHub Actions will be a robust way to maintain the epochs branches. The immediate motivation for this is to increase the frequency of Edge and Safari runs on Azure Pipelines from every 6 to every 3 hours: https://github.com/web-platform-tests/wpt/issues/18669#issuecomment-546062584 -- wpt-commits: b482734e5092c5f5a6aadc66aa1c599742f2dc67 wpt-pr: 19873 Differential Revision: https://phabricator.services.mozilla.com/D53465
31597bd8e738af5fbea1f2d166e73eaf6a73e9d8: Bug 1590623 [wpt PR 19842] - Move relationship properties out of aria_attributes.idl, remove string version, a=testonly
Rakina Zata Amni <rakina@chromium.org> - Mon, 04 Nov 2019 10:46:25 +0000 - rev 564674
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1590623 [wpt PR 19842] - Move relationship properties out of aria_attributes.idl, remove string version, a=testonly Automatic update from web-platform-tests Move relationship properties out of aria_attributes.idl, remove string version We want to ship non-relationship aria properties on ElementInternals first, because the relationship properties are still WIP. We are also removing the string version of the relationship properties. Change-Id: Iccd73d1c9b1b31a431764e7989083dac43ed76d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874751 Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Meredith Lane <meredithl@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#709359} -- wpt-commits: b7ac8324bfc2ab9f0351056a1ea8381a845f6106 wpt-pr: 19842 Differential Revision: https://phabricator.services.mozilla.com/D53464
e890da8a14117cbdce745abe78e6f5ee7233ea03: Bug 1590272 [wpt PR 19817] - Don't trigger :focus-visible matching if a meta-key was pressed., a=testonly
Alice Boxhall <aboxhall@chromium.org> - Mon, 04 Nov 2019 10:46:20 +0000 - rev 564673
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1590272 [wpt PR 19817] - Don't trigger :focus-visible matching if a meta-key was pressed., a=testonly Automatic update from web-platform-tests Don't trigger :focus-visible matching if a meta-key was pressed. Also, move UpdateHadKeyboardEvent() call into KeyboardEventManager::KeyEvent(). Happy to revert the latter change if folks don't like it, but it seemed logically consistent with e.g. gesture detection. Bug: 920458 Change-Id: Ia423a0533325314ae4f83e619337b5a81af0f4c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871715 Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#709357} -- wpt-commits: 69646ed085ad3e2295549c3ecf3f5caa9e4e1e9a wpt-pr: 19817 Differential Revision: https://phabricator.services.mozilla.com/D53463
77f4518a5433a96aa28405f91d94228e83e3135f: Bug 1585800 [wpt PR 19477] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 02 Oct 2019 22:01:50 +0000 - rev 564672
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1585800 [wpt PR 19477] - Update wpt metadata, a=testonly wpt-pr: 19477 wpt-type: metadata Differential Revision: https://phabricator.services.mozilla.com/D53462
c8c878dfb658d6c8b8ece4130bd28c65b1d54949: Bug 1585800 [wpt PR 19477] - [workers] Correct variable name, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Mon, 04 Nov 2019 10:46:12 +0000 - rev 564671
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1585800 [wpt PR 19477] - [workers] Correct variable name, a=testonly Automatic update from web-platform-tests [workers] Correct assertions This test generates subtests based on the value of a binding named `unexpected`. Prior to this commit, no such binding was declared by the test, so it failed to declare any subtests and instead produced a ReferenceError. Currently, testharness.js interprets this result as a failing "single-page test," although it will soon be more accurately reported as a harness error [1]. Update the test to assert the presence of the properties as originally intended. [1] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md Co-authored-by: Ms2ger <Ms2ger@gmail.com> -- wpt-commits: ca2983ebb0a61e076e13ce848ab999293093f4cb wpt-pr: 19477 Differential Revision: https://phabricator.services.mozilla.com/D53461
f3e99fd78d1dc3d8aede5a106e6aea7aea55fbcc: Bug 1585812 [wpt PR 19480] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 03 Nov 2019 13:34:04 +0000 - rev 564670
Push 12351 by ffxbld-merge at Mon, 02 Dec 2019 11:32:26 +0000
Bug 1585812 [wpt PR 19480] - Update wpt metadata, a=testonly wpt-pr: 19480 wpt-type: metadata Differential Revision: https://phabricator.services.mozilla.com/D53460
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip