917205af08c0d042325797003bc9051e96aa8159: Bug 1621802 [wpt PR 22200] - WebXR - hit test - add WPTs for input-source-based hit test, a=testonly
Piotr Bialecki <bialpio@chromium.org> - Sat, 14 Mar 2020 11:28:25 +0000 - rev 518838
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621802 [wpt PR 22200] - WebXR - hit test - add WPTs for input-source-based hit test, a=testonly Automatic update from web-platform-tests WebXR - hit test - add WPTs for input-source-based hit test - add WPT tests for hit test based off of input sources - reduce float point precision threshold in Chrome's mock implementation - minor refactor in webxr-test.js Changes: Change-Id: I4385ae38cc5f731d69981ad86cdadcd8ab078b40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015182 Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#749867} -- wpt-commits: dca4a8fe363d03216a7f4bc00218e0f1456a4e83 wpt-pr: 22200
ea93b29b3730ecb9638b270bfd4348028bde8b96: Bug 1622066 [wpt PR 22223] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 12 Mar 2020 22:36:43 +0000 - rev 518837
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622066 [wpt PR 22223] - Update wpt metadata, a=testonly wpt-pr: 22223 wpt-type: metadata
de8e977f2569f494a95830e63c57d280225e2e71: Bug 1622066 [wpt PR 22223] - InsecureRequestPolicy: Add WPTs for subresource fetching from workers, a=testonly
Eriko Kurimoto <elkurin@google.com> - Sat, 14 Mar 2020 11:28:17 +0000 - rev 518836
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622066 [wpt PR 22223] - InsecureRequestPolicy: Add WPTs for subresource fetching from workers, a=testonly Automatic update from web-platform-tests InsecureRequestPolicy: Add WPTs for subresource fetching from workers This CL adds tests for subresource fetching from HTTP(S) scheme url dedicated workers and shared workers. Currently, we have subresource fetching tests from ONLY data: URL dedicated workers . In this CL, we improve the test coverage by adding subresource fetching tests from HTTP(S) scheme url workers which are more normal. Bug: 989399 Change-Id: Icf83cd359fa64df94c5ff93210c7a1c7bce12944 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2077321 Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Eriko Kurimoto <elkurin@google.com> Cr-Commit-Position: refs/heads/master@{#749578} -- wpt-commits: 8916fa4113bf2a2724822f0b0c726d3a5705dd64 wpt-pr: 22223
7f39fa2a2626c839fd32230e6f254f2009d56fe5: Bug 1622019 [wpt PR 22220] - Revert "rtcpeerconnection: dont fire signalingstatechange from close()", a=testonly
Henrik Boström <hbos@chromium.org> - Sat, 14 Mar 2020 11:28:12 +0000 - rev 518835
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622019 [wpt PR 22220] - Revert "rtcpeerconnection: dont fire signalingstatechange from close()", a=testonly Automatic update from web-platform-tests Revert "rtcpeerconnection: dont fire signalingstatechange from close()" This reverts commit e8e1bf919cd15279406f11e5c2418f5d70fa897e. Reason for revert: Breaks detecting if pc closed for other reasons, like laptop lid closing. This CL should be re-landed with the following fix incorporated: https://chromium-review.googlesource.com/c/chromium/src/+/2097979 Original change's description: > rtcpeerconnection: dont fire signalingstatechange from close() > > RTCPeerConnection.close() shall not fire events. It doesn't already for > iceconnectionstate/connectionstate > > BUG=699036 > > Change-Id: I771cdd81c3bbdb4312a623e96f8150be8471d906 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1959042 > Commit-Queue: Harald Alvestrand <hta@chromium.org> > Reviewed-by: Harald Alvestrand <hta@chromium.org> > Cr-Commit-Position: refs/heads/master@{#727965} TBR=hta@chromium.org,guidou@chromium.org,philipp.hancke@googlemail.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 699036, 1060547 Change-Id: I85312331cb91fc7bc78326b8c86c68bca7d06e56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100973 Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#749842} -- wpt-commits: 13587fef36cd1df92d3e38d6e5916b380e971857 wpt-pr: 22220
615472b72a74b59c1221ddffdade622f437fee36: Bug 1618467 [wpt PR 22001] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 12 Mar 2020 22:11:30 +0000 - rev 518834
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1618467 [wpt PR 22001] - Update wpt metadata, a=testonly wpt-pr: 22001 wpt-type: metadata
e444034cc8294edda4299d1b8da3952c4b329b19: Bug 1618467 [wpt PR 22001] - MixedContent: Add WPTs for subresource fetching from workers, a=testonly
Eriko Kurimoto <elkurin@google.com> - Sat, 14 Mar 2020 11:28:04 +0000 - rev 518833
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1618467 [wpt PR 22001] - MixedContent: Add WPTs for subresource fetching from workers, a=testonly Automatic update from web-platform-tests MixedContent: Add WPTs for subresource fetching from workers This CL adds tests for subresource fetching from HTTP(S) scheme url dedicated workers and shared workers. Currently, we have subresource fetching tests from ONLY data: URL dedicated workers and shared workers. In this CL, we improve the test coverage by adding subresource fetching tests from HTTP(S) scheme url workers which are more normal. Dedicated workers inherit the parent document's CSP headers for inside settings, so worker scripts don't need to include policyDeliveries. On the other hand, shared workers use the CSP headers specified by worker scripts as inside settings, so worker scripts need to include policyDeliveries. Here, policyDeliveries means: Content-Security-Policy: block-all-mixed-content In this CL, tools/util.py is modified because |obj| is parsed from json as OrderedDict so type(obj) == dict is always false. Bug: 1056500 Change-Id: I1881a5609a08c96f8d358e26673efac0ad70e6b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2077319 Commit-Queue: Eriko Kurimoto <elkurin@google.com> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#749527} -- wpt-commits: a02045acebc136b7ba04900ab780a163809fdf3c wpt-pr: 22001
6ba3311cbf0ebc0f71012e506bc752f6a66667f4: Bug 1622006 [wpt PR 22216] - Flaky test: Increase fetchReport timeout 1s -> 4s, a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Sat, 14 Mar 2020 11:27:55 +0000 - rev 518832
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622006 [wpt PR 22216] - Flaky test: Increase fetchReport timeout 1s -> 4s, a=testonly Automatic update from web-platform-tests Flaky test: Increase fetchReport timeout 1s -> 4s Waiting up to 1s is probably too low. Some bots (mac) are not getting the expected report on time. See: https://bugs.chromium.org/p/chromium/issues/detail?id=1061029#c4 TBR=yhirano@chromium.org Bug: 1061029 Change-Id: Id3f24cc9ea216e6686ccbb4d534592dd9849a82c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100931 Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#749710} -- wpt-commits: a207a569b5a4afdebafdf80cc6f59d766455c333 wpt-pr: 22216
5fb4974c00e3cb5410826591128681287baed2a0: Bug 1621656 [wpt PR 22189] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 12 Mar 2020 16:23:31 +0000 - rev 518831
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621656 [wpt PR 22189] - Update wpt metadata, a=testonly wpt-pr: 22189 wpt-type: metadata
9388adba44f0b536b7a4d58fcf0e50d61e5d884c: Bug 1621656 [wpt PR 22189] - [Trusted Types] Ignore `require-trusted-types-for` in non-secure contexts., a=testonly
Mike West <mkwst@chromium.org> - Sat, 14 Mar 2020 11:27:46 +0000 - rev 518830
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621656 [wpt PR 22189] - [Trusted Types] Ignore `require-trusted-types-for` in non-secure contexts., a=testonly Automatic update from web-platform-tests [Trusted Types] Ignore `require-trusted-types-for` in non-secure contexts. Bug: 1059554 Change-Id: Ib92e3ebfb3148aa4634a4f1f29cbbfd8d45fdfdb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098076 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#749697} -- wpt-commits: 525cdf91d59303beb0d542f347b8330c3d6ee077 wpt-pr: 22189
95ce2ba147c6bfa5da943e8d190d28c97c038279: Bug 1618913 [wpt PR 22156] - [Gecko Bug 1618913] Preload Firefox instances in wpt harness, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 14 Mar 2020 11:27:06 +0000 - rev 518829
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1618913 [wpt PR 22156] - [Gecko Bug 1618913] Preload Firefox instances in wpt harness, a=testonly Automatic update from web-platform-tests Preload Firefox instances in wpt harness The wpt harness spends a lot of time — about 20% of the total runtime on Linux64 — between tests. The majority of this is shutting down and restarting the Firefox instance under test. To reduce this overhead we add the option to preload a Firefox instance which can be immediately used when a new session is required. This makes the slow process of creating a profile and starting the browser asynchronous. Testing shows that this cuts the between-test time to between a half and a third of the previous value. The cost of this change is that we are adding background load at the time tests are running, which could influence the results and add randomness. However that seems unlikely unless we are right on the edge of the system performance. Differential Revision: https://phabricator.services.mozilla.com/D64954 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1618913 gecko-commit: 1da2a939d9cf39156b38b639f77d777b0821eb4e gecko-integration-branch: autoland gecko-reviewers: karlcow -- wpt-commits: 660e74817e4d0ac21ad21de6764e9ac2902704bd wpt-pr: 22156
c1dcacb7aa9603803de410e9941f9ea18987190b: Bug 1621463 [wpt PR 22173] - Update mozrunner to 7.8.0, a=testonly
pyup-bot <github-bot@pyup.io> - Sat, 14 Mar 2020 10:39:13 +0000 - rev 518828
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621463 [wpt PR 22173] - Update mozrunner to 7.8.0, a=testonly Automatic update from web-platform-tests Update mozrunner from 7.7.0 to 7.8.0 -- wpt-commits: cf05949faebaec0009dc50d494cd91b0175df678 wpt-pr: 22173
e6134f9533d2765414538835cde2ccd1b44ab7e4: Bug 1621893 [wpt PR 22211] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 12 Mar 2020 16:11:52 +0000 - rev 518827
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621893 [wpt PR 22211] - Update wpt metadata, a=testonly wpt-pr: 22211 wpt-type: metadata
2d987ea12f79e36d69920ac12488e15f954a792f: Bug 1621893 [wpt PR 22211] - Add WPT for DedicatedWorker + COEP reporting, a=testonly
Makoto Shimazu <shimazu@chromium.org> - Sat, 14 Mar 2020 10:39:05 +0000 - rev 518826
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621893 [wpt PR 22211] - Add WPT for DedicatedWorker + COEP reporting, a=testonly Automatic update from web-platform-tests Add WPT for DedicatedWorker + COEP reporting This CL adds tests to check the support of COEP reporting for requests initiated by a dedicated worker. So far, Chrome has a bug that the context url is the page's url where the dedicated worker is created. This bug is going to be fixed once PlzDedicatedWorker is shipped (with additional work for integration between PlzDedicatedWorker and COEP reporting). Bug: 1060837 Change-Id: I12291646c4d5a80d89c8894548acdb186f4a14be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100059 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Auto-Submit: Makoto Shimazu <shimazu@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#749623} -- wpt-commits: 1e35b4abf6e896af2ce0b342967cae6da8df612d wpt-pr: 22211
a9cebd53a328ba387ac8930dc7ec26e3f6462af2: Bug 1620103 [wpt PR 22097] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Mar 2020 15:24:50 +0000 - rev 518825
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1620103 [wpt PR 22097] - Update wpt metadata, a=testonly wpt-pr: 22097 wpt-type: metadata
b668fe11677dcad7a586878d6b826582e9c375c3: Bug 1620103 [wpt PR 22097] - Add a Trust Tokens argument to Fetch's RequestInit., a=testonly
David Van Cleve <davidvc@chromium.org> - Sat, 14 Mar 2020 10:38:57 +0000 - rev 518824
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1620103 [wpt PR 22097] - Add a Trust Tokens argument to Fetch's RequestInit., a=testonly Automatic update from web-platform-tests Add a Trust Tokens argument to Fetch's RequestInit. This CL expands the Fetch API, when the runtime-enabled feature "TrustTokens" is enabled, to include a new experimental parameter `trustTokens` denoting a request to execute a Trust Tokens protocol step (https://github.com/wicg/trust-token-api) alongside the fetch at hand, by adding request headers and processing corresponding response headers. This is an experimental interface that will be used in an origin trial. It only needs to support fetches from frames (i.e., it is OK from a usability perspective for the origin trial if the parameter is not populated when fetch is called from other settings). The main parts of the CL are: - as specified in the linked explainer, expand Fetch's RequestInit dictionary with a new trustToken parameter, specifying a single Trust Tokens protocol operation of token issuance, token redemption, or request signing; - add this data to blink::ResourceRequest and associated objects, so that it gets copied to network::ResourceRequest in blink::PopulateResourceRequest. Test: - Adds integration tests in //content to ensure that calling the API results in the right ResourceRequest members being populated. Change-Id: I5c5b0c0ed5450eeb80c19be856f62941e50ec0e1 Bug: 1043118 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036648 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: David Van Cleve <davidvc@chromium.org> Cr-Commit-Position: refs/heads/master@{#749622} -- wpt-commits: f7e2ea2c50c4d23549d07cd24c7a96fc3f203d96 wpt-pr: 22097
decf30eff2bb575f3e1f906695cbe9a96996290e: Bug 1621690 [wpt PR 22192] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 12 Mar 2020 15:15:09 +0000 - rev 518823
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621690 [wpt PR 22192] - Update wpt metadata, a=testonly wpt-pr: 22192 wpt-type: metadata
60d63a608908a41bd5afe59007e73484f6729894: Bug 1621690 [wpt PR 22192] - [COEP] CacheStorage > reporting API > WPT tests, a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Sat, 14 Mar 2020 10:38:42 +0000 - rev 518822
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1621690 [wpt PR 22192] - [COEP] CacheStorage > reporting API > WPT tests, a=testonly Automatic update from web-platform-tests [COEP] CacheStorage > reporting API > WPT tests When a response is blocked by CORP because of the COEP header, check the reporting API is worker. This patch adds 4x2=8 new WPT tests. For every 4 context: - Document - SharedWorker - DedicatedWorker - ServiceWorker For the 2 headers: - Cross-Origin-Embedder-Policy - Cross-Origin-Embedder-Policy-Report-Only Bug: 1059727, 1031542, 887967 Change-Id: I797e36d0cfc982862e85dbc9a49c661fee46bf85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096687 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#749603} -- wpt-commits: a24e1f169812387a3f332a075fe8fee28cef4588 wpt-pr: 22192
0f2f823b599293166b82ceecd15b452de8b48382: Backed out 2 changesets (bug 1620778) for causing test_autocomplete_mac_caret.xhtml failures
Ciure Andrei <aciure@mozilla.com> - Sun, 15 Mar 2020 16:04:36 +0200 - rev 518821
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Backed out 2 changesets (bug 1620778) for causing test_autocomplete_mac_caret.xhtml failures Backed out changeset 66f97d1cf94a (bug 1620778) Backed out changeset eda75d901f4c (bug 1620778)
00683827be1afd7193afc84f64f8b45523c3a2ae: Bug 1622562 - Remove flags parameter from ReportCompileError. r=arai
Tom Schuster <evilpies@gmail.com> - Sun, 15 Mar 2020 00:04:58 +0000 - rev 518820
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1622562 - Remove flags parameter from ReportCompileError. r=arai Differential Revision: https://phabricator.services.mozilla.com/D66880
66f97d1cf94abf84e2fafddfbf440d4dfd8fba35: Bug 1620778 - Re-skip a test on non-cocoa.
Emilio Cobos Álvarez <emilio@crisal.io> - Sun, 15 Mar 2020 14:06:05 +0100 - rev 518819
Push 37217 by ccoroiu@mozilla.com at Sun, 15 Mar 2020 21:37:59 +0000
Bug 1620778 - Re-skip a test on non-cocoa. This was done for debugging, but I forgot to do this before submitting. MANUAL PUSH: Bustage fix on a CLOSED TREE
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip