Automatic update from web-platform-tests
[WPT] Only load *.mojom.js through loadMojoResources
* Load other resources separately
* Throw from loadMojoResources when a path is not /gen/.../*.mojom.js
Bug: 1116600
Change-Id: I4f9dbc4459583480ce202e65c789397422a282fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358904
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798922}
--
wpt-commits: db9a10cb04de8883c4c04dd57683436f6bb47917
wpt-pr: 25062
Automatic update from web-platform-tests
Make table-model-fixup-2 wait for load
This was previously flaky, especially in Safari. This flakiness
came from the race between the images loading and the tests running.
--
wpt-commits: c799cfd8162cc02ee15b6372124a3395a1375954
wpt-pr: 25059
Automatic update from web-platform-tests
[nativeio] NativeIO: Add setLength
The MacOS sandbox does not allow calling base::File::SetLength() from
the renderer directly, see crbug.com/1084565. The call to setLength is
therefore routed through the browser process, which likely decreases
performance and increases complexity. Another option would be to create
a SeatbeltExtensionToken that allows to pierce the sandbox on MacOS for
a single file. As this would likely lead to more complex code, we
decided that going through the browser process is the better option for
now.
Bug: 914488
Change-Id: Idc58d804e19751a2e37cfeb5c645f778edf4639c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2257855
Commit-Queue: Richard Stotz <rstz@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799005}
--
wpt-commits: c9e08236b532473b460dca5daa717dcb8824d7dc
wpt-pr: 24575
Automatic update from web-platform-tests
[wptrunner] Two small fixes for python3 compatibility (#24993)
--
wpt-commits: 60adaca26fe896827da39bebd75fcbb329f5b975
wpt-pr: 24993
Automatic update from web-platform-tests
Consider directly composited images as covering the PictureTilingSet
For elements with will-change:transform or directly composited images
the raster scale is not updated in response to transform scale
changes. Once the scale gets especially large, the interest rect
computed by blink starts to become less than the layer bounds.
This ends up setting a recorded_viewport_ on RasterSource that is also
less than the layer bounds. If the interest rect gets small enough, it's
possible that tiles that are in view are not completely covered by the
RasterSource. This means that we won't create tiles (much less assign
them GPU memory and schedule them) in PictureLayerTiling::CreateTile. We
did not see this with the previous implementation of directly composited
images, since the content layer never had an interest rect computed.
This change fixes this specifically for directly composited images by
always considering its raster source as covering the entire layer. This
is the definition of directly composited images (has a DrawImageRectOp
that draws into the entire layer). This allows the in view tiles to be
created, then rasterized and activated and the image no longer
disappears.
I looked into fixing the general case (see comments in the bug) but
given the regression for the images scenario and the fact that we'd like
to get a fix merged for 85, I took an approach to just fix directly
composited images.
Bug: 1110141
Change-Id: Ice3cf25508585f116edd7317718292ec9ad8a7ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358888
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Daniel Libby <dlibby@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#798836}
--
wpt-commits: 3a326c47caa930616ce141bebb5c3e382cdc896c
wpt-pr: 25034
Automatic update from web-platform-tests
[Web Payment] No shipping with secure payment confirmation.
Before this patch, invoking PaymentRequest API with secure payment
confirmation method identifier and options to request shipping or
contact information was considered valid.
This patch throws RangeError in PaymentRequest constructor if secure
payment confirmation method identifier is requested together with
shipping or contact information.
After this patch, it's not possible to request secure payment
confirmation method together with shipping or contact information.
Bug: 2348410
Change-Id: I3e01f9b758645a1653533f41da9688c453199b03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359554
Reviewed-by: Liquan (Max) Gu <maxlg@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798755}
--
wpt-commits: 2f79fdd170945fb988568274655c348551e5723f
wpt-pr: 25047
Automatic update from web-platform-tests
Origin isolation: report that opaque origins are origin-isolated
This reports data: and sandboxed iframes as always origin-isolated,
according to the window.originIsolationRestricted property. This is
done regardless of the process isolation state or the presence/absence
of the Origin-Isolation header.
The web platform tests were revamped in the following ways:
* Sandboxed iframes and data: URL tests were split into -yes and -no
variants, to ensure that the parent frame didn't influence the
result. For sandboxed iframes in particular, the -no variant was not
tested previously, and was failing until after the code changes here.
* Additional tests for javascript: URLs were introduced, as an earlier
version of this CL would trigger a DCHECK on opaque-origin pages
navigating to javascript: URLs.
* Shared code was factored out. The .html files are now just wrappers
that delegate to resources/*-test.mjs files.
Bug: 1095653
Change-Id: I69a1f388250d1364dd33c365c936a76546add5b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2334103
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798741}
--
wpt-commits: 4b36a443e9efb8f486c1c4c567048847b03ad80c
wpt-pr: 24897
Automatic update from web-platform-tests
[WPT] Refactor WebBluetooth tests to use test-only-api.js
And remove unused mojom.js files.
Bug: 1094512
Change-Id: Ibe8503d72fff30b96248c14647b65481c06c7b2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350482
Commit-Queue: Robert Ma <robertma@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Auto-Submit: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798691}
--
wpt-commits: ca3e490761daa8332d2e236fe2c318065cbeae50
wpt-pr: 24971
Automatic update from web-platform-tests
Do not create a stacking context for CSS clip
This patch extracts out the stacking context grouping properties from
ComputedStyle::HasGroupingProperty, and uses this for the stacking
context decision. This has the effect of not creating a stacking context
for clip which, unlike clip-path, does not create a stacking context:
https://drafts.fxtf.org/css-masking-1/#propdef-clip
Bug: 1115003
Change-Id: I4bd5d3c61a2bb34a56a089cbeaca260fc9bf2eb4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358473
Commit-Queue: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Auto-Submit: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798712}
--
wpt-commits: bb4b0c3786c93b34e10888ea489c6fc29fbe41da
wpt-pr: 25041
Automatic update from web-platform-tests
Make canvas-createImageBitmap-e_srgb.html run cross-browser
There were harness errors in Edge, Firefox and Safari:
https://wpt.fyi/results/html/canvas/element/manual/wide-gamut-canvas/canvas-createImageBitmap-e_srgb.html?run_id=657990001&run_id=659880001&run_id=633480001&run_id=663850001
The cause for that was the convertToBlob call not correctly wrapped in a
step in testCreateImageBitmapFromColorManagedBlob.
That was only the first of multiple errors fixed here:
- not handling image or video decode failures, causing timeouts
- failures at the end of testCreateImageBitmapFromColorManagedBlob
would not have failed the test because promise rejections were
not handled
- failing in cryptic ways if ImageData dataUnion isn't supported
These issues were fixed while also modernizing the tests to use more
modern APIs where available, like img.decode() and fetch().
Change-Id: Ia8d0086a2d216dd291c9429460f8a79f8f4fd1c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359991
Reviewed-by: Wan-Teh Chang <wtc@google.com>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798674}
--
wpt-commits: 0833f372662afd7b4a7cf7d060dec9cb16c40f9f
wpt-pr: 25037
Automatic update from web-platform-tests
Python3: Use str type for payload (#25029)
--
wpt-commits: 18e23ca711b7a079f90b721edb30e5d4cb9ec8e8
wpt-pr: 25029
Automatic update from web-platform-tests
Replace os.path.split with .dirname or .basename where appropriate (#25008)
Most of the changes made by:
> git grep -lF os.path.split | xargs sed -i '' 's/os\.path\.split(\(.*\))\[0\]/os.path.dirname(\1)/g'
That gets some things wrong, so all changes were vetted and some fixed
or simplified.
--
wpt-commits: 0f986ae5b0865c0bef78e41e35d144e30a14b2e7
wpt-pr: 25008
Automatic update from web-platform-tests
Misc bug fixes/features for webcodecs/VideoEncoder
- don't clear the error callback prior to calling it
- implement encodeQueueSize to signal backpressure
- add extra error logging for VpxVideoEncoder
- disable vp9 profiles 1 and 3 (not yet implemented)
And opportunistically mark a number of inputs
in IDL as required
- timestamp (its required for creation of VideoFrame internally)
- error and output callbacks (duh).
Remove ? from duration input dictionary. Its not required,
no need to null.
Bug: 1094166, 1116617
Change-Id: I9577bc42d1f24c2ec14885401e87337ba0937e43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355276
Commit-Queue: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798473}
--
wpt-commits: 5d19229558e94c90c23b05df9260836e093df1b2
wpt-pr: 25027
Automatic update from web-platform-tests
Fix range-percent-intrinsic-size-2 reference
This test worked on Mozilla due to the adoption of orient="vertical"
and the native sizing of the range control. It failed on Chromium
because min-content was less than 30px. This new version appears
to pass on both Chromium and Mozilla.
Fixed: 1108796
Change-Id: Ie5cbaaff6c78f7658931e8d63860383e3501f5ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355567
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798460}
--
wpt-commits: d99ec97e0fa94d907d0c0e968690b88d17f749e1
wpt-pr: 25016
Automatic update from web-platform-tests
[mathml] Implement the mpadded element
Implement the mpadded element [1]. This CL also renames LayoutNGMathMLSquareRoot to LayoutNGMathMLBlockWithAnonymousMrow, since now it is not just used by msqrt.
[1] https://mathml-refresh.github.io/mathml-core/#adjust-space-around-content-mpadded
Bug: 6606
Change-Id: I8243bb8e5fb0975a407bf12275487434283cfe4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2288388
Commit-Queue: Rob Buis <rbuis@igalia.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798451}
--
wpt-commits: 1098ebbf49ec20a5298b9d58ff463a223e76c513
wpt-pr: 24664
Automatic update from web-platform-tests
WebXR: Fix DOM overlay for out of process iframes (OOPIF)
Propagate the "is_xr_overlay" fullscreen request type flag for OOPIF
requests via mojo, and ensure that visibility is set correctly for
out of process container iframe elements.
Note for testing: Currently, Chrome on Android only enforces site
isolation for sites with login active, and not on low memory devices.
Run with the --site-per-process command line flag to override this.
Bug: 1101193
Change-Id: Ic8736e90f28fbda2d6cb1f665cbd0804c3f38cc3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283968
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798382}
--
wpt-commits: 8cdb75336b65e31e0278082e74927e5be2045b5a
wpt-pr: 24988
Automatic update from web-platform-tests
WebXR: Handle same-process iframe DOM overlay
For same-process iframes, propagate the Document-level IsXrOverlay flag,
and use the correct element as the overlay layer.
This moves the document->SetIsXrOverlay setters from xr_system to
fullscreen to ensure it gets applied consistently. There are multiple
documents that need updating when iframes are being used. (Handling
out-of-process iframes needs additional logic that's being added
in a followup CL.)
Bug: 1101193
Change-Id: Icf80e65e1b927888c6140acbc998ed90d469b5e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283823
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798312}
--
wpt-commits: f06a1d2d8af7ed4d1e74228521ddfa044f7f05c8
wpt-pr: 25002
Automatic update from web-platform-tests
Enable transformed rasterization for most layers
Background: transformed rasterization is used to render sharp text in a
composited layer with fractional transform. It snaps the composited
transform of the layer to whole pixels, then applies the fraction
during rasterization.
Previously we disallowed transformed rasterization in blink for directly
composited layers (excluding backface-visibility:hidden and trivial 3d
transforms such as translateZ(0)), especially for will-change:transform
because change of fractional transform would cause re-rasterization
which would defeat the purpose of will-change:transform.
Now for a layer that was not eligible for transformed rasterization,
calculate the initial raster translation which achieves sharp text
rendering with the initial transform. When the transform of the layer
changes, keep its original raster translation to avoid invalidation
of tilings, to ensure animation performance. The rendered result will
be blurry during animation but the initial rendering result is sharp.
Remove blink-side transformed rasterization conditions and let cc
decide it based on screen and draw transforms of the layers.
Bug: 1111195
Change-Id: If0455be2f29e69cd7152c951626e6e8cc143b5bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351164
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798268}
--
wpt-commits: 364882ddd6119c1d97b501faadf19251253a5bd9
wpt-pr: 25006
Automatic update from web-platform-tests
Perform a microtask checkpoint after updating timelines.
Updating timelines can enqueue tasks related to ready and finish
promises which should run before animation events and updated
rendering.
Bug: 1116020
Change-Id: Ica1927bb3921eef574abeaca23bb198dda658ccd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354164
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798259}
--
wpt-commits: c7ecececab97dedc736c9198670937bcfb5520a4
wpt-pr: 25013
Automatic update from web-platform-tests
[wpt] Support MojoJS in Chrome Dev (#24979)
Automatically download mojojs.zip and turn on relevant flags for Chrome
Dev. Follow-up to #24739.
--
wpt-commits: 4398d74fea97068f29499dcd1c6d6d6b268b9940
wpt-pr: 24979
Automatic update from web-platform-tests
[COOP] access reporting: use camelCase for attributes.
This make it easier to access an attribute using Javascript. This also
make both the network reports and the ReportingObserver to have the same
attribute names.
Previously, the spec was based on CSP, which has both camelCase and hyp-hen.
Today, we report thing using camelCase instead:
- DocumentPolicyViolationReport,
- FeaturePolicyViolationReport,
- DeprecationViolationReport,
- InterventionViolationReport
Bug: 922191
Change-Id: Ic875163b16acf5083ed8197266fc23034f2c5005
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352926
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798143}
--
wpt-commits: cdd1562260dba7a1babc019afd8b6cb6d73714f9
wpt-pr: 25009
Automatic update from web-platform-tests
Add tests for input and change event properties
See https://github.com/whatwg/html/issues/5453.
The <select> test doesn't appear to work on Safari, but I can't figure out how to fix it without a Mac.
--
wpt-commits: 47f659d346db0b1ed0d336fdee81a16214f2a6d1
wpt-pr: 24995
Automatic update from web-platform-tests
Fix test cases intended for special URLs
Test cases in the setters_tests.json file below comment "Can’t switch
from URL containing username/password/port to file" are intended for
special URLs. But there are two test cases with "gopher" scheme, which
is not special anymore.
Fix these test cases by changing "gopher" to special scheme "https".
Note. Test cases for non-special URLs are below comments "Can’t switch
from special scheme to non-special" and "Can’t switch from non-special
scheme to special".
--
wpt-commits: 6c74b7e43c9a1f6dc3dc529e427e2ef96152409e
wpt-pr: 25010
Automatic update from web-platform-tests
[COOP] access reporting. Remove tests about reporting in enforced mode.
COOP access reporting will ship only in 'reporting-only'. Support for
the 'enforced-mode' has been dropped for now.
This patch remove all the tests related to the part dropped.
Bug: 1090273
Change-Id: If3081929f2409e33afe9891353afb5045df07662
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352809
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798085}
--
wpt-commits: df19afe000c2a6f7075c529608c5f4f2317d3a42
wpt-pr: 24977
Automatic update from web-platform-tests
COOP: change handling of redirects
This CL changes the handling of redirects in COOP to match
https://github.com/whatwg/html/pull/5739. Instead of comparing a
response to the current document, we will compare it to the last entry
in the redirect chain.
Change-Id: I73a3926a8827733974d7c08b7f3553da06435ac3
Bug: 1108292
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339988
Commit-Queue: Camille Lamy <clamy@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798083}
--
wpt-commits: ed42d5908c6008e054919281f893b7f5cecd5e75
wpt-pr: 24990
Robert Ma
Sam Sneddon
moz-wptsync-bot
Richard Stotz
Stephen McGruer
Daniel Libby
Rouslan Solomakhin
Domenic Denicola
autofoolip
Philip Rogers
Philip Jägenstedt
Kagami Sascha Rosylight
Domenic Denicola
ziransun
youennf
Chris Cunningham
Mason Freed
Rob Buis
Klaus Weidner
Xianzhu Wang
Robert Flack
arthursonzogni
cfredric
Rimas Misevičius
Camillo Bruni
Lucas Furukawa Gadani
David Bokan
Camille Lamy