Automatic update from web-platform-tests
CSP: Fix report-to for frame-ancestors violation
Content-Security-Policy 'frame-ancestors' checks are performed in the
browser during the navigation. Violation reports, however, are sent
through Blink. When using the reporting API (via the 'report-to'
directive), we need to use the correct URL for the report, since that
URL's origin will be used to match the reporting endpoints. Otherwise,
we end up not sending reports or, worse, sending them to the wrong
endpoints.
This change addresses that and adds a WPT.
In the future, we should avoid sending the reports through Blink at
all.
Bug: 2324115
Change-Id: Iccab0cfe178900844d97aa7989922b014d02efcf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2747378
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862787}
--
wpt-commits: 8a4a29f7491c950550528576757f77d0e7f973f1
wpt-pr: 27992
Automatic update from web-platform-tests
CSP: Enhance WPTs to check inline and eval blockedURIs
This adds a few assertions to Web Platform Tests for Content Security
Policies checking if inline script execution and eval are allowed, so
that they also ensure that the blockedURI in the CSP violation matches
'inline' or 'eval'.
Bug: 563976
Change-Id: Ie2b93fe838768703e652dcfd5bd25b1334abcf57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2743762
Auto-Submit: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862765}
--
wpt-commits: accfb3c80f500136eafb2969a821845299883ca1
wpt-pr: 27961
Automatic update from web-platform-tests
Convert some import assertion and JSON module tests to .any.js
Convert some .html import assertion and JSON module tests to .any.js in
order to get free dedicated worker coverage for those tests.
The ServiceWorker tests are being dropped because JSON modules are
not yet supported in ServiceWorkers. See
https://chromium-review.googlesource.com/c/chromium/src/+/2728110.
Bug: 1132413
Change-Id: Ifb13ddd69aab54a1f55b9bf0ad517590b4afce6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2728289
Commit-Queue: Dan Clark <daniec@microsoft.com>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862697}
--
wpt-commits: 6e8f21a9b3a88264b34dbffcaa94186cb81cca74
wpt-pr: 27852
Automatic update from web-platform-tests
WebKit export of https://bugs.webkit.org/show_bug.cgi?id=222739 (#28029)
* Test cross-origin function caching
* Test cross-origin function "length" value
* Test cross-origin function "name" value
--
wpt-commits: ad101699843022c27b920579d04b2f33e8b00430
wpt-pr: 28029
Automatic update from web-platform-tests
Skip layout shift tracking for more invisible elements
Besides the current conditions, e.g. visibility:hidden, opacity:0
(which is checked in PaintInvalidator instead of LayoutShiftTracker)
etc., also ignore the following invisible elements:
- For texts:
- if the font is not renderable
- if the text contains all whitespaces
- For blocks:
- if it doesn't have any decorations, and doesn't have any children.
For performance and to reduce risk of false-negative of layout shift
tracking, the conditions are kept simple. If a developer still get
unexpected layout shift for invisible elements, we can suggest adding
visibility:hidden to the element to explicitly disable layout shift
tracking on the element.
See https://ct.skia.org/results/cluster-telemetry/tasks/chromium_perf_runs/wangxianzhu-ChromiumPerf-5677/html/index.html
for the change of overall CLS score with this CL.
Bug: 1099350
Change-Id: Ib7e89e0331663572d1eef511976556e8b2a96a96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2743811
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862593}
--
wpt-commits: 48e5e3c75c9d0df0b18ee7628a98bbc85250eedd
wpt-pr: 28030
Automatic update from web-platform-tests
Fix perspective interpolation test to allow 0 as value (#28036)
> As very small <length> values can produce bizarre rendering results and stress the numerical accuracy of transform calculations, values less than 1px must be treated as 1px for rendering purposes. (This clamping does not affect the underlying value, so perspective: 0; in a stylesheet will still serialize back as 0.)
--
wpt-commits: 416fe32178df91d925759e8deccdb9c7330995f5
wpt-pr: 28036
Automatic update from web-platform-tests
HighlightAPI: Implement iteration for Highlight and HighlightRegistry.
Implemented by copying the elements in these setlike types into another data structure (a variant of Vector) at the beginning of the iteration, and then iterating through these copies instead of the live data structures.
There are currently similar approaches for setlike/maplike iterations in for example AudioParamMap and FontFaceSet. See bug 1185385 for more info.
Bug: 1185385
Change-Id: I7e2e36d63e80cca6623c8c67ad22db0079965568
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2748417
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Sanket Joshi <sajos@microsoft.com>
Commit-Queue: Fernando Fiori <ffiori@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#862577}
--
wpt-commits: a3c7285a875ae5a0ab8ea942f153418948277e1a
wpt-pr: 28034
Automatic update from web-platform-tests
Add tests for assert type: 'js' and type: 'javascript'
These should both fail since JavaScript modules can only be loaded if
there is no type assertion:
import "./foo.js" assert { type: "js"};
import "./foo.js" assert { type: "javascript"};
Add tests for both cases.
Bug: 1132413
Change-Id: Ia856ff02aff8381bb642fba2e8fafc32bc6f5793
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2751188
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Dan Clark <daniec@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#862573}
--
wpt-commits: 10c4f27e8f323196865882bf407439ba236c7bd3
wpt-pr: 28019
Automatic update from web-platform-tests
Resizer in visibility:hidden element should not be hit
Bug: 1185968
Change-Id: Ib030e107fc299db4c39bdf55ac4a246ef58d4759
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2757172
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862566}
--
wpt-commits: 3615932a650e9ccf9274eebd52c26c62fbbe78b5
wpt-pr: 28061
Automatic update from web-platform-tests
Cookie Domain WPTs: Clean up cookies at the end of each test
This attempts to fix an issue where cookies from previous tests stick
around and interfere with cookie-line test assertions in subsequent
tests, when many tests are run in series.
This adds cookie deletion to the end of each test in
wpt/cookies/domain which was failing to do so. (There are tests in
other directories that fail to clean up cookies, but those will be
handled separately.)
Change-Id: I26d0f342e401f4bbcf8ba318683861fa5a45faac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2748837
Reviewed-by: Steven Bingler <bingler@chromium.org>
Commit-Queue: Lily Chen <chlily@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862525}
--
wpt-commits: 50b6da2d34f7bb1084ad919a865f6d3ab8aa3ae1
wpt-pr: 28015
Automatic update from web-platform-tests
Make :host()/:host-context() accept a single <compound-selector>
This aligns us with Firefox/spec, and makes it possible to remove
the awkward dynamic specificity calculation code from SelectorChecker.
Added some basic parsing WPTs since it appeared to be missing.
I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/ztanzClftBA/
Fixed: 1143404
Test: wpt/css/css-scoping/host-[context]-specificity-00[n].html
Change-Id: I146849d6beba971353f58ff136577a9faacf1c7d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2747498
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862425}
--
wpt-commits: a9a2c239455f884f0a3656d1fb0f615ef0e32c2b
wpt-pr: 28052
Automatic update from web-platform-tests
CSP: Fix history inheritance WPTs for firefox
The Web Platform Tests introduced with https://crrev.com/c/2728996
fail on Firefox because of several reasons, which this CL addresses:
- We must consider bfcache when navigating back from history
(img.onerror will not fire again).
- The cleanup function to close popup sometimes fails.
- The history-iframe.sub.html test was flaky, although only on the wpt
runner (I could not reproduce manually in Firefox).
Fixed: 1186710
Change-Id: I8be49897e60a6d6c8cd4c99660ae756707964048
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2752230
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862415}
--
wpt-commits: a94cf1a48033a003f2db5e0d6bc7370344b984c7
wpt-pr: 28023
Automatic update from web-platform-tests
NativeIO: Disalllow use on opaque origins
With this change, the global storageFoundation object is set to null on
opaque origins by the renderer.
While opaque origins were correctly disallowed by the browser process,
triggering the BadMessage lead to a crash of the entire browser. This
change also fixes this bug.
Bug: 1186722
Change-Id: I562bd9a8610b08e40e8ef318e8d50a6116699f27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2751110
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Richard Stotz <rstz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862393}
--
wpt-commits: 758d63c44e7958d2bce3581efcfa766c31ba6f81
wpt-pr: 28026
Automatic update from web-platform-tests
Distribute widths evenly among code points in SynthesizeGraphemeWidths
Previously we did not consider the possibility of a typographic unit
containing multiple surrogate pairs, and could as an effect "lose" part
of the width.
Distribute the width evenly among code points instead to at least get
some sort of consistency.
Bug: 879361
Change-Id: Id87495ff91acd602c3bfa2ae747bcdfce864ad01
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2749236
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#862376}
--
wpt-commits: a336f0f67eebe4f58bf1b52e126d849c564236bb
wpt-pr: 28022
Automatic update from web-platform-tests
Handle secondary edges in custom property cycles
The cycle detection in StyleCascade is not correct. Any secondary edges
coming from a cycle are also detected as in-cycle, even if they aren't.
Explanation of how the new cycle detection works:
- AutoLock is used to "lock" a property that's currently being resolved.
- It's instantiated at the start of ResolveCustomProperty,
ResolveVariableReference, and ResolvePendingSubstitution. No other
places.
- All "lock" means is that the property we're resolving is pushed to
CascadeResolver.stack_.
- When we're trying to resolve a var(), a cycle is detected by looking
for a given property in that stack. If the property is found, the
stack index is set as the cycle_start_, and the current size of the
stack is set as the cycle_end_. The idea is that all the properties
in the range [cycle_start_, cycle_end_) are in a cycle, and are
therefore invalid.
- As we come back up the regular call stack, we check the InCycle flag
to see if a (nested) variable resolution has detected a cycle, and if
we're still inside it.
Where the old code went wrong, was that we assumed that once a cycle was
detected, we would not push anything new onto CascadeResolver.stack_
until we were out of the cycle. Hence, once a cycle was detected,
anything reachable from the start of the cycle would be detected as
in-cycle.
This is regression from the StyleCascade project (since M82), although
nobody reported the issue.
Unfortunately this exposed that two tests relied on the buggy cycle
detection. These tests have been temporarily disabled/rebaselined.
Change-Id: If7bbaad084c001c4f3349a7a4050b0a5bd33139b
Fixed: 1187282
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2749195
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862369}
--
wpt-commits: 678cbc9eb44fcc4b303b076cf758e96295d8fee3
wpt-pr: 28035
Automatic update from web-platform-tests
Update css-backgrounds tests after a Skia change
A Skia change to pattern drawing led to pixels diffs of
1 on lots of pixels within the gradient images. Add fuzzy
tags to address this.
Bug: 1185506
Change-Id: I400ccbfeb5991b178b04e0141f6363a41fa2b9c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2752931
Auto-Submit: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#862357}
--
wpt-commits: 1089574d5ccb1913ecd22a0cf0fac81e9de9e03e
wpt-pr: 28039
Automatic update from web-platform-tests
webrtc wpt: add test for video clockrate
measure the rtp clockrate of video using the getSynchronizationSources API which should be approximately 90000.
Bug: None
Change-Id: I9d8578c9a31b13e94970679df4289b3bd3a79f0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2649930
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862346}
--
wpt-commits: bef3b0d61dcde21449e57e6798a4975d9345b564
wpt-pr: 27334
Automatic update from web-platform-tests
Revert "Improve counterscroll handling"
This reverts commit c3a63721ee0613b73066c5166109c0dd054b926e.
Reason for revert: Caused CLS benchmark regressions. Some are expected,
like the change in shift-while-scrolled.html. Some look problematic,
e.g. some results changed from 0 to non-0. Needs investigation.
Original change's description:
> Improve counterscroll handling
>
> Previously we tracked the maximum scroll offset in a viewport to ignore
> counterscroll shifts, but it failed when
> - There were multiple scrollers scroll at the same time. Tested by
> external/wpt/layout-instability/shift-with-counterscroll-2.html.
> - An invisible shift was countered by both scroll and transform, e.g.
> move layout location by 100px, scroll by -50px, and transform by
> -50px. Tested by
> external/wpt/layout-instability/shift-with-counter-scroll-and-transform.html
>
> Now let PaintPropertyTreeBuilder track scroll delta, and pass the delta
> to LayoutShiftTracker.
>
> Bug: 1182213
> Change-Id: I18366ff7bc0e96374a954bee1c1600b582681dd8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741240
> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
> Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
> Reviewed-by: Steve Kobes <skobes@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#861702}
Bug: 1182213, 1186894
Change-Id: I69ccdb7d132f73618777530e932578fbadee35e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2754072
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862256}
--
wpt-commits: 482859cfb029e9d64ee19027133b6fd3a67bff44
wpt-pr: 28046
Automatic update from web-platform-tests
NativeIO: Improve WPT test coverage and fix tests
This CL makes the following changes to the Web Platform Tests for
NativeIO:
* Add a WPT that no files with invalid filenames can be created.
* Add the empty string to the list of invalid file names.
* Fix missing awaits in the capacity allocation WPTs and check that
the operation succeeds.
* Always return the full capacity in the capacity allocation WPTs.
* Fix formatting issues and missing words in the affected tests.
Bug: 1181766, 1181770
Change-Id: Ie0ae69b167e9dec6f73ef1062049f3f0cd850fa4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2745153
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#862146}
--
wpt-commits: 4d3d985ba9096a8c3fa4b1967b4d41e64948e68b
wpt-pr: 27953
Automatic update from web-platform-tests
Perform xrReferenceSpace_originOffsetBounded.html validations with an active XRFrame (#28024)
Right now validations are run inside the requestReferenceSpace promise callback which may not have an active XRFrame state
--
wpt-commits: 5c7cc7fefd4844660361370a9cadd81e57c3dfec
wpt-pr: 28024
Automatic update from web-platform-tests
Introduce a --no-fail-on-unexpected-pass flag. (#28000)
* Introduce a --no-fail-on-unexpected-pass flag.
Very similar to --no-fail-on-unexpected but this will only tolerate
unexpected PASS/OK results.
--
wpt-commits: 20a1af1f1acb81b89b8b51c168f380e0098b69d1
wpt-pr: 28000
Automatic update from web-platform-tests
Fetch: additional port blocking in response to NAT Slipstream v2
See also https://github.com/whatwg/fetch/pull/1148
--
wpt-commits: 54e43b60de1e364c6d3b94d86bb1932cefb0bb04
wpt-pr: 27990
Automatic update from web-platform-tests
CSP: Don't trigger spv for frame-ancestors
We should not trigger frame-ancestors securitypolicyviolation events
in the parent frame, since this is a cross-origin leak.
Fixed: 1186611
Bug: 1186611
Change-Id: Iee57e198c17b6827dde199431b31b87b82e0e276
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2747500
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Cr-Commit-Position: refs/heads/master@{#861885}
--
wpt-commits: 60cbac188135ca19ebe866c1ded17fffb733402e
wpt-pr: 27977
