ae5161d58f26d31c5bc597a85b178f35547b2990: Bug 1612272 [wpt PR 21508] - Fix beacon referrer test to pass when blocked for mixed content, a=testonly
Yoav Weiss <yoav@yoav.ws> - Tue, 04 Feb 2020 13:17:01 +0000 - rev 513240
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612272 [wpt PR 21508] - Fix beacon referrer test to pass when blocked for mixed content, a=testonly Automatic update from web-platform-tests Fix beacon referrer test to pass when blocked for mixed content (#21508) -- wpt-commits: d65350a4df0b65794ff408ea06e2c3668031a9ea wpt-pr: 21508
46e00454909e8a3eb4f08d6fa23f9c85c1d4dee1: Bug 1612113 [wpt PR 21491] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 30 Jan 2020 09:48:20 +0000 - rev 513239
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612113 [wpt PR 21491] - Update wpt metadata, a=testonly wpt-pr: 21491 wpt-type: metadata
28ba507f0cf138dfb7a3395be32f45f8f5f3b0ff: Bug 1612113 [wpt PR 21491] - Let color-scheme affect the initial color value., a=testonly
Rune Lillesveen <futhark@chromium.org> - Tue, 04 Feb 2020 13:16:53 +0000 - rev 513238
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612113 [wpt PR 21491] - Let color-scheme affect the initial color value., a=testonly Automatic update from web-platform-tests Let color-scheme affect the initial color value. We used to have a root element color value based on an internal UA sheet value, but this is not according to spec since it affects the initial value for the color property, hence setting the color value to 'initial' should result in a used value that depends on the color-scheme for that element. Initial value for the color property is canvastext, but we do not yet ship color-scheme aware system colors, so instead we implement this as a method on ComputedStyle which is color-scheme aware and currently return black for light and white for dark. The devtools test changes are basically a revert of the necessary changes done when we introduced -internal-root-color. Bug: 939811 Change-Id: I63477751e1fe4aa3ce8292e8a3fc2cdb1dd3afbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027469 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#736763} -- wpt-commits: 6a7bdc42ab3688499203b154772cccc3f01c0f5b wpt-pr: 21491
809ce7b3c3e1a43d6f32248962bbe5a0cafcf407: Bug 1612208 [wpt PR 21499] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 30 Jan 2020 00:30:51 +0000 - rev 513237
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612208 [wpt PR 21499] - Update wpt metadata, a=testonly wpt-pr: 21499 wpt-type: metadata
904e7c61f713735a6f2285b0245ed70cdf1ce02f: Bug 1612208 [wpt PR 21499] - Add WPTs for requiring a completed navigation in a portal before activation, a=testonly
Kevin McNee <mcnee@chromium.org> - Tue, 04 Feb 2020 13:16:45 +0000 - rev 513236
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612208 [wpt PR 21499] - Add WPTs for requiring a completed navigation in a portal before activation, a=testonly Automatic update from web-platform-tests Add WPTs for requiring a completed navigation in a portal before activation We've started rejecting activation of a portal contents with no committed navigations. We already have a test relating to 1P navigation restrictions. We introduce WPTs to cover this condition more generally. We also convert one of the bail out conditions for transferring session history to a DCHECK as this is now covered by the rejection. Bug: 942198 Change-Id: I2f4a9aae5aa3461c7c5e25a677f659a7e7d7ffc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028755 Commit-Queue: Kevin McNee <mcnee@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#736597} -- wpt-commits: 4017c884097baf142893dd7aeebdb972c6832d7c wpt-pr: 21499
1e5bd74fa1d30f403dc58183f914a69a97ce9b91: Bug 1612079 [wpt PR 21487] - Make sure layout is triggered when changing clip-path resource, a=testonly
Fredrik Söderquist <fs@opera.com> - Tue, 04 Feb 2020 13:16:38 +0000 - rev 513235
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612079 [wpt PR 21487] - Make sure layout is triggered when changing clip-path resource, a=testonly Automatic update from web-platform-tests Make sure layout is triggered when changing clip-path resource When changing the 'clip-path' property on an (SVG) element we need to recompute the visual rect since it includes contributions from the clip bounds (as well as the mask and filter bounds). This wasn't happening, which meant that the element wouldn't repaint properly if the old bounds were smaller than the new bounds. Add some detection of bounds-affecting changes to SVGResourcesCache and Make use of that in SVGResourcesCache::ClientStyleChanged() to mark the element for layout if needed so that its bounds are updated properly. Fixed: 1045915 Change-Id: Ia08904945b26c382e0b9c90c15b7cc45d40434cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023561 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#736486} -- wpt-commits: c206a3b3b144ae607acb040303a7740073eba8a0 wpt-pr: 21487
bb93278786085af2fe73ea0fba77fff8ba4c9965: Bug 1610848 [wpt PR 21342] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 29 Jan 2020 20:57:16 +0000 - rev 513234
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1610848 [wpt PR 21342] - Update wpt metadata, a=testonly wpt-pr: 21342 wpt-type: metadata
1115d18d354179286b5e3238b293fed01d78f936: Bug 1610848 [wpt PR 21342] - Avoid dereferencing a null pointer in list_interpolation_function, a=testonly
haozhe <haozhes@chromium.org> - Tue, 04 Feb 2020 13:16:29 +0000 - rev 513233
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1610848 [wpt PR 21342] - Avoid dereferencing a null pointer in list_interpolation_function, a=testonly Automatic update from web-platform-tests Avoid dereferencing a null pointer in list_interpolation_function The current code doesn't catch the case where non_interpolatable_value is null for the interpolation_list. This patch add a protection for this situation. Bug: 1039733 Change-Id: I442a56e4984285dfe524dcd669fae9f4da0a7f94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011167 Commit-Queue: Hao Sheng <haozhes@chromium.org> Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Xida Chen <xidachen@chromium.org> Reviewed-by: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#736481} -- wpt-commits: 71a49b6a48ef83837562485f1349793a858717d6 wpt-pr: 21342
51fcc90f0f62239eb191d871d4633471d4955b40: Bug 1611981 [wpt PR 21473] - Validate remote ICE parameters in RTCIceTransport.start(), a=testonly
Steve Anton <steveanton@chromium.org> - Tue, 04 Feb 2020 13:16:24 +0000 - rev 513232
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1611981 [wpt PR 21473] - Validate remote ICE parameters in RTCIceTransport.start(), a=testonly Automatic update from web-platform-tests Validate remote ICE parameters in RTCIceTransport.start() Bug: 1044521 Change-Id: Ib7350579495f4774a05980c763d1fe453a4c179b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024074 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Steve Anton <steveanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#736443} -- wpt-commits: be7ccc19c940268e31b3eb77acab4275526777dc wpt-pr: 21473
4f7f4a13dcf632a6c8ed2dd4b57fad5350c8fa88: Bug 1612018 [wpt PR 21480] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 29 Jan 2020 18:44:01 +0000 - rev 513231
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612018 [wpt PR 21480] - Update wpt metadata, a=testonly wpt-pr: 21480 wpt-type: metadata
86a7e6e535540896129a604e78e9113a16b079f2: Bug 1612018 [wpt PR 21480] - SVG default forced colors, a=testonly
Alison Maher <almaher@microsoft.com> - Tue, 04 Feb 2020 13:16:16 +0000 - rev 513230
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612018 [wpt PR 21480] - SVG default forced colors, a=testonly Automatic update from web-platform-tests SVG default forced colors This change adds the default color and fill forced colors for SVG elements (WindowText). Before this change, SVG fill and color would default to black in forced colors mode, making certain elements un-readable. Bug: 970285 Change-Id: I68ecb4769a502fbb1c4ceb27ba0b3d21205aeb45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026147 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/master@{#736418} -- wpt-commits: 0db0c67f7499409479ec020cf636184a986f7fcd wpt-pr: 21480
4564c31e6fb62aa31c167c5f1065346c8e75cae8: Bug 1612023 [wpt PR 21483] - SharedWorker: Add WPT for upgrade-insecure-requests, a=testonly
Eriko Kurimoto <elkurin@google.com> - Tue, 04 Feb 2020 13:16:11 +0000 - rev 513229
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612023 [wpt PR 21483] - SharedWorker: Add WPT for upgrade-insecure-requests, a=testonly Automatic update from web-platform-tests SharedWorker: Add WPT for upgrade-insecure-requests This CL adds upgrade-indecure-requests web-platform-tests for module shared workers "sharedworker-module" is added to spec.src.json and it auto-generates tests. Bug: 824646 Change-Id: I3d75f4b7b1af93c12548331ad46e5f812205ea00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024249 Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Commit-Queue: Eriko Kurimoto <elkurin@google.com> Cr-Commit-Position: refs/heads/master@{#736229} -- wpt-commits: c3240b66a895c68eff2f67331cbffecfb08573c5 wpt-pr: 21483
3d3fd18bea7dc123eb7c37163e537e5bbb4c0775: Bug 1611856 [wpt PR 21448] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 29 Jan 2020 16:28:34 +0000 - rev 513228
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1611856 [wpt PR 21448] - Update wpt metadata, a=testonly wpt-pr: 21448 wpt-type: metadata
4588c5df9b6c37a1ed78261779805fa683fb61f6: Bug 1611856 [wpt PR 21448] - Cancel rather than block navigations which violate portals 1P rules., a=testonly
Jeremy Roman <jbroman@chromium.org> - Tue, 04 Feb 2020 13:16:02 +0000 - rev 513227
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1611856 [wpt PR 21448] - Cancel rather than block navigations which violate portals 1P rules., a=testonly Automatic update from web-platform-tests Cancel rather than block navigations which violate portals 1P rules. Since this can lead to a WebContents with no committed entries, deal with that case in the browser-side Activate logic, by rejecting activations which occur before we can say with certainty that we will load a page (i.e. navigation commit). Bug: 1046121,1034740,942198 Change-Id: Icd219dc0bb1e4a9ab6fdc433f8644c14e69964e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015768 Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Lucas Gadani <lfg@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#736369} -- wpt-commits: 3888d4d05c82a951afb63fd0d20a38bb5ea3bf90 wpt-pr: 21448
b5841170ad2bcf1bdbbdb2e5c890c6ee1a79cf33: Bug 1610696 [wpt PR 21330] - Add interfaces/webrtc-svc.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 04 Feb 2020 13:15:56 +0000 - rev 513226
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1610696 [wpt PR 21330] - Add interfaces/webrtc-svc.idl, a=testonly Automatic update from web-platform-tests Add interfaces/webrtc-svc.idl (#21330) Source: https://github.com/tidoust/reffy-reports/blob/7ae7c91/ed/idl/webrtc-svc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/639926932 -- wpt-commits: 7bd4977b248e1f464f26f3c0b99d17676871de45 wpt-pr: 21330
b3450e9c5b09afa339b5ff59675c8b2f2c9be817: Bug 1609418 [wpt PR 21191] - [Security] Implement the context switch for COOP., a=testonly
Arthur Hemery <ahemery@chromium.org> - Tue, 04 Feb 2020 13:15:51 +0000 - rev 513225
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1609418 [wpt PR 21191] - [Security] Implement the context switch for COOP., a=testonly Automatic update from web-platform-tests [Security] Implement the context switch for COOP. This CL lands the Cross-Origin-Opener-Policy "changes to navigation", as per: https://gist.github.com/annevk/6f2dd8c79c77123f39797f6bdac43f3e In practice, it forces a BrowsingInstance switch when we have a COOP mismatch. This is necessary but not sufficient, as we want to ensure the following behavior: (1) window.open() returned WindowProxy is closed when we know that we need to switch. (2) opener is null in opened popups. (3) window.name is empty in opened popups. This CL solves (2). Currently (1) is untested and will follow in a different patch (tests under development by pmeuleman@ at https://github.com/web-platform-tests/wpt/pull/21161) and (2) needs to be updated with some other state in DidCommit. Bug: 922191 Change-Id: I7d5169f7d53bfc28ea01a1a03c7658e0645bc492 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985013 Commit-Queue: Arthur Hemery <ahemery@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#736344} -- wpt-commits: 2ae8e39b7116213662bcc5357394d4418651211c wpt-pr: 21191
d0b7b05f1c400bf030daa7999c6d10d52b7cbbf7: Bug 1612017 [wpt PR 21479] - Add interfaces/web-locks.idl and modify test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 04 Feb 2020 13:15:46 +0000 - rev 513224
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612017 [wpt PR 21479] - Add interfaces/web-locks.idl and modify test, a=testonly Automatic update from web-platform-tests Add interfaces/web-locks.idl and modify test (#21479) Closes https://github.com/web-platform-tests/wpt/pull/21329 -- wpt-commits: 1c5d0a817201698ce43de1e0bf34c3e612dd2c82 wpt-pr: 21479
9c170776cc7f57f6e6445eda54148ef5b29df5d1: Bug 1612029 [wpt PR 21484] - SharedWorker: Remove debug-output in referrer-policy WPT, a=testonly
Eriko Kurimoto <elkurin@google.com> - Tue, 04 Feb 2020 13:15:40 +0000 - rev 513223
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1612029 [wpt PR 21484] - SharedWorker: Remove debug-output in referrer-policy WPT, a=testonly Automatic update from web-platform-tests SharedWorker: Remove debug-output in referrer-policy WPT This CL removes debug-output in referrer-policy web-platform-tests. This file shouldn't be added but unintentionally included in the CL: https://chromium-review.googlesource.com/c/chromium/src/+/2023710 Bug: 824646 Change-Id: If0775cebd63d53dd0510b5d64ce2a643998455cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026829 Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Eriko Kurimoto <elkurin@google.com> Cr-Commit-Position: refs/heads/master@{#736296} -- wpt-commits: 074719e3660000659cd074b8a59de69bd9b90cd7 wpt-pr: 21484
06c1844da78f53eda0f8e35a252255ad0302e8b1: Bug 1611791 [wpt PR 21432] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 29 Jan 2020 11:04:06 +0000 - rev 513222
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1611791 [wpt PR 21432] - Update wpt metadata, a=testonly wpt-pr: 21432 wpt-type: metadata
2fb8f6c788f127ad9fbe01b09e0b8511e71836f2: Bug 1611791 [wpt PR 21432] - Stop dispatching SMIL events while seeking, a=testonly
Fredrik Söderquist <fs@opera.com> - Tue, 04 Feb 2020 13:15:32 +0000 - rev 513221
Push 37112 by btara@mozilla.com at Tue, 11 Feb 2020 21:47:36 +0000
Bug 1611791 [wpt PR 21432] - Stop dispatching SMIL events while seeking, a=testonly Automatic update from web-platform-tests Stop dispatching SMIL events while seeking Based on [1], 'beginEvent' and 'endEvent' should only be dispatched for elements that are active at the seeked-to time and elements that were active at the previous/old/seeked-from time but are inactive at the seeked-to time (respectively). 'repeatEvent's should not be disaptched while seeking. To handle this, extend the TimingUpdate helper class with a map that tracks what interval the active elements had before the seek operation, and whether the timing update operation is a seek operation (called "fast-forward" since we end up moving in the forward direction regardless of the actual seek direction). Apart from that, the dispatching of 'repeatEvent's are also inhibited, as well as the notifications of repeats in general. [1] https://www.w3.org/TR/SMIL3/smil-timing.html#q114 Bug: 1039886 Change-Id: I17d91b1355858ee0b916d4fa46b9572e685e40e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020947 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#736289} -- wpt-commits: e03feecc468b65aadc66b24bf76dbd0d6acfff5b wpt-pr: 21432
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip