Automatic update from web-platform-tests
change csp tests that use Report-To header to Reporting-Endpoints
- Report-To header is deprecated in favour of Reporting-Endpoints
- Remove virtual test suite for reporting-api/ since Reporting is
enabled by default now
Bug: 1288953
Change-Id: Ief31a92e1f6c85f771c97ddd291fad5f99aef477
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3418664
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Rodney Ding <rodneyding@google.com>
Cr-Commit-Position: refs/heads/main@{#968738}
--
wpt-commits: d12af0a83a62babf178d1176d43c0f2fe0fe4f3d
wpt-pr: 32568
Automatic update from web-platform-tests
Fix wrong integrity value subresource-integrity-partial-image.html
The current integrity value in
wpt/preload/subresource-integrity-partial-image.html seems wrong.
It seems to match zero length content. This CL updates the value
to match the image generated by
element-timing/resources/progressive-image.py?name=square100.png
Change-Id: Ie2abe6edb25c7b1a2f4e5e5cc9c2f0bb6d323c73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3412624
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968709}
--
wpt-commits: e65aefee7fc98dcf5cbfdb7345ceaa988ce9a0a1
wpt-pr: 32549
Automatic update from web-platform-tests
[WPT] BFCache: focus should be kept around BFCache
This CL adds a test to confirm that,
when page gets into and out of BFCache,
- Focus should be kept and
- blur/focus events are not fired.
The current results are
Safari: Pass
Firefox: Focus remains the same but blur/focus events are fired.
Chrome: Focus is lost.
See https://github.com/whatwg/html/pull/6696
for other status and implementation bug links etc.
Bug: 1107415, 1253728, https://github.com/whatwg/html/issues/5878
Change-Id: I2bb9a420de19f24d7010917f7e6ce54cba8212fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3198456
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968703}
--
wpt-commits: a1e49a05bf46345316fd04bb4b22e5e7e8d9bc70
wpt-pr: 31084
Automatic update from web-platform-tests
[WPT] Eligibility: dedicated and shared workers (#31228)
When there are dedicated workers/shared workers,
Chrome: The page is not BFCached.
Firefox: The page is BFCached.
Safari: The page is BFCached for dedicated workers.
Shared workers are not supported.
Bug: 1146955
Change-Id: Ia901715436e1a0c64c68ad5b537e99f685825489
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3220944
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Fergal Daly <fergal@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968294}
Co-authored-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
--
wpt-commits: 485d32c18d07b58d75c9997794987cfce3c35246
wpt-pr: 31228
Automatic update from web-platform-tests
[scheduling APIs] Remove scheduler.currentTaskSignal prototype
Removing this to make room for task attribution tracking
(crrev.com/c/3310850), which also needs the V8 APIs to get/set
continuation preserved embedder data. Since we don't know if we want to
pursue shipping this in its current form, we'll make room for the task
attribuion code rather than change the V8 API to handle multiple values.
Removing this API also removes the creation of implicit task signals,
which involved some slight refactoring. In particular, DOMTaskQueue is
modified to hold the priority (used in DOMTask for tracing and metrics)
and DOMTask is modified to take a potentially null AbortSignal and
non-null DOMTaskQueue instead of a non-null TaskSignal (potentially
implicit) and a task runner.
Bug: 995862, 1291129
Change-Id: I103e520f1e7d1f236a4845f099f0d0a662d1c017
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3449072
Reviewed-by: Nate Chapin <japhet@chromium.org>
Commit-Queue: Scott Haseley <shaseley@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968689}
--
wpt-commits: 27191fcd3a0ef231294b92ac77c01f2f0445e362
wpt-pr: 32756
Automatic update from web-platform-tests
[Reland][FedCM Refactor] Rename FederatedCredential#logout()->logoutRPs()
Also renames FederatedAuthRequest::Logout() parameter type and return
type:
- LogoutStatus -> LogoutRpsStatus
- LogoutRequest -> LogoutRpsRequest
This CL differs from
https://chromium-review.googlesource.com/c/chromium/src/+/3441287 in that
it fixes the v8_federated_credential_logout_rps_request.h import
BUG=1294412
Change-Id: I8b322cbdffcbd020da35b3f80836937055d93366
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3448930
Reviewed-by: Yi Gu <yigu@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968674}
--
wpt-commits: 625a123e538d25f6cf4b647a3a269d98c70651f3
wpt-pr: 32754
Automatic update from web-platform-tests
bluetooth: Fix crash in invoking some APIs when the context is gone
Fix the failure/crash when invoking APIs exposed by the bluetooth module
while the context is gone. As mojo service has the mechanism to detect
context existence and set service bounded state accordingly, relying on
checking at service bounded state and throwing an exception when the
remote service is not bounded.
Bug: 1282963
Change-Id: I6b6b2ee2724c7eb73bcd29b5d5c2fbdbaf325683
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3425468
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Jack Hsieh <chengweih@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968643}
--
wpt-commits: 12d947f8e364341d9b8411509c278dfbc72a35f7
wpt-pr: 32614
Automatic update from web-platform-tests
Make css_parsing_utils::ConsumeInteger() clamp negative calc() to 0.
When parsing a non-negative integer, if the given value is calc() that evaluates to a negative number,
the value should be valid at parse-time and clamped to 0 at computed/used time.
In this CL, we add kNonNegativeIntegers enum entry to CSSPrimitiveValue::ValueRange
and use it in CSSMathFunctionValue::ClampToPermittedRange.
Bug: 1295078
Change-Id: Ic12de0e234a798cc22221856b402fd83332137b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3446701
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: 박중헌 <pjh0718@gmail.com>
Cr-Commit-Position: refs/heads/main@{#968639}
--
wpt-commits: e6bb9e18b2c8bb5ef8eba5a9f8b8efae553ad522
wpt-pr: 32742
Automatic update from web-platform-tests
Shadow DOM: Fix :focus selector behavior for shadow hosts
If a shadow node is focused, all ancestor shadow hosts should match
to :focus pseudo selector.
Such shadow hosts should not match to :focus-visible pseudo selector.
https://html.spec.whatwg.org/C/#selector-focus
> its shadow root shadowRoot is not null and shadowRoot is the root of
> at least one element that has the focus.
The new behavior matches to Firefox and Safari.
* Merge some web tests into a WPT.
Bug: 1014091
Change-Id: Ibbe841c18324f1cf18dba04138e4e5e102ea31f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3439312
Reviewed-by: Mason Freed <masonf@chromium.org>
Reviewed-by: Mohamad Ahmadi <mahmadi@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968637}
--
wpt-commits: bd4437121db36c3d87cbc209d89d18c10fd97806
wpt-pr: 32744
Automatic update from web-platform-tests
URLPattern: Set unmatched optional groups to undefined instead of ''.
This addresses the issues raised in:
https://github.com/WICG/urlpattern/issues/162
The main changes in this CL are:
1. The webidl is modified to allow passed back undefined. I'm told
real webidl should support `(USVString or undefined)` here, but our
webidl compiler does not support that. So we use `any` instead.
2. We must examine if the WTF::String is null or not before populating
the returned array. If its null, then we convert to undefined
instead.
Bug: 1292699
Change-Id: I27a0be2567bb9ce4592ca15a5216fd5a58bdbf17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3428631
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968611}
--
wpt-commits: 111b696bdbb572a89065ce2d3cd524f7d6798301
wpt-pr: 32650
Automatic update from web-platform-tests
Correct calculated sRGB result (small error, enough to alter 0..255 result)
--
wpt-commits: 909c0dd89d4a2b43a1e6a3216b427f64556795e7
wpt-pr: 32735
Automatic update from web-platform-tests
Window Placement: Fix prerendering test invalid placement requests
Blink clamps sync placement estimates to available screen bounds.
Tests should avoid requesting bounds outside the available bounds.
See more context from https://crrev.com/c/3428148
FWIW, content_shell window placements are not really valid:
- It does not actually implement window.moveTo()
- It always reports window.screen[X|Y] as 0
Bug: 1294721
Change-Id: If0933bc086ba10388a0aef0488460862536bff6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3443651
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Mike Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968418}
--
wpt-commits: 3b013e74de9c4f1d88625837cc10fb5e21a4351a
wpt-pr: 32733
Automatic update from web-platform-tests
ComputedStyle may be null for disconnected elements
Should not use NOTREACHED() since it is a valid case to have null
ComputedStyle for elements which are not connected to a document.
Bug: 1291680
Change-Id: I901b68a004311d935fda2d46671b0c1d87c98e0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3443433
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968270}
--
wpt-commits: ed88da243901447e7f7518314cabce6bf9c27fdf
wpt-pr: 32741
Automatic update from web-platform-tests
Handle parallel flows established inside a block-in-inline.
If a block inside an inline gets overflowed, this may result in a
parallel flow [1]. We need to treat this separately from the regular
inline content that might follow after the block.
We used to end up resuming a block-in-inline in the same fragmentainer
where it had already broken. This caused both DCHECK failures and
incorrect layout. We need to wait until we get to the next
fragmentainer, before resuming the block-in-inline.
At the same time we need to make sure that regular inline content that
comes after the overflowed block is correctly resumed in the current
fragmentainer.
[1] https://www.w3.org/TR/css-break-3/#parallel-flows
Bug: 1291939
Change-Id: I955693509d8e2743cf53b01ba20bd65ee8a336c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3442958
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968053}
--
wpt-commits: 138e4b8078933960dd0c9f386b56742811cc8c27
wpt-pr: 32713
Automatic update from web-platform-tests
[inert] Replace mentions of "expressly inert" with "inert"
The concept of "expressly inert" in the HTML spec was a remnant from the
past. It no longer made sense, and wasn't implemented anywhere.
I removed it in https://github.com/whatwg/html/pull/7565
This patch replaces all mentions with just "inert".
No change in behavior.
Bug: 692360
Change-Id: I5bb76e633b13ee244eb69ad5e99ce9d9705073aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3438605
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/main@{#968045}
--
wpt-commits: c909db1182a7aa150e7aca7574b7baf55c2675a3
wpt-pr: 32686
Automatic update from web-platform-tests
Upstream additions to css/css-color/parsing from WebKit
--
wpt-commits: ba2fedf81ef53da873735b5f14ddbac97cd1708d
wpt-pr: 32711
Automatic update from web-platform-tests
[@container] Out-of-flow replaced not containers in legacy
Out-of-flow positioned replaced elements take the legacy path for layout
if the container for positioning is a legacy object. That is the case
for LayoutView, which is a legacy object but does not otherwise force
legacy layout objects.
Make sure we either don't skip style recalc for such elements, or resume
recalc during AttachLayoutTree() to not leave anything incomplete after
a lifecycle update.
Bug: 1289850
Change-Id: I59a7043eaf073fbf031ca90164788cd5b60f50eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3439924
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#967754}
--
wpt-commits: db6e3a5d72aa41963087750ff5fa99e77eb047d4
wpt-pr: 32722
Automatic update from web-platform-tests
Refactor summarizing code in resources/test/conftest.py.
--
Fix typo in test_immutable_prototype.html.
--
Handle Exposed=* in more places in idlharness.
--
Add a test for Exposed=*.
--
wpt-commits: c682f1320a71e669b276147b45907b0aac1da27e, 0618cd7553015b869d2fdcdc3637cfb0fc94a432, 3cce22cc8f5f3fc92c25564e8805dabc4d4ef7f7, f5e30b174ccda1acb80c0f45a13c0e3ebbec7bc5
wpt-pr: 32673
Automatic update from web-platform-tests
Docs: correct tutorial ToC
d7de25c4ac8a0185b2e8f39eb3a0e1c780b04e9c was probably the result of a rebase gone bad.
--
wpt-commits: b0f2a3d41dbcf8043d5438992851203b821f740b
wpt-pr: 32724
Automatic update from web-platform-tests
[@container] Resume skipped style recalc for dropped LayoutObjects
LayoutObject::IsChildAllowed() may disallow child LayoutObjects of
certain types. We are typically not able to detect this at style recalc
time, which means we may skip style recalc for size query containers
which will not be able to resume recalc in NGBlockNode. Detect this at
AttachLayoutTree time and force-resume the style recalc like we do for
legacy layout.
Bug: 1294268
Change-Id: I0a1a3d4437d84d913c3a75b056ae993601a5fb51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3440249
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#967745}
--
wpt-commits: 7ae1a8ce81b4fb0792b431dbcc41e20c4fee5517
wpt-pr: 32721
Automatic update from web-platform-tests
Cookies: Test IDN/non-ASCII in domain attributes
This is for https://github.com/httpwg/http-extensions/issues/1707.
I took some inspiration from #26170 and used a python server instead of a header file in order to better control which bytes are served as part of the header.
The test runs exclusively on the élève. subdomain through opening a new window that then runs all test and reports back to the main test window.
--
wpt-commits: 48d28a82aa28f3491e525b7c32b8bb1cdfdaf6f6
wpt-pr: 32620
Automatic update from web-platform-tests
import.meta.url should include the URL fragment
Update workers/modules/shared-worker-import-meta.html to expect import.meta.url to include
the URL fragment. This matches the behavior of both WebKit and Blink.
See https://github.com/whatwg/html/issues/5162 for more information.
--
wpt-commits: 1c1e48b75ebf98fd3db4af8a330fcb6109942ce5
wpt-pr: 32704
Automatic update from web-platform-tests
New tests for filter() function (#23429)
--
wpt-commits: 7f8942c429a66fa5225d2b9cebcf72d09afd9b14
wpt-pr: 23429
Automatic update from web-platform-tests
Add missing assert statements in equals.tentative.html.
The test cases for CSSMathClamp should have assert statements.
Bug: 1292345
Change-Id: I0bed4e8efe615f8e27d240c17ab71123c76aa62e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3439447
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: 박중헌 <pjh0718@gmail.com>
Cr-Commit-Position: refs/heads/main@{#967546}
--
wpt-commits: ee152b0d418ebbd82454f101b1b0fc7ebc5d5ac4
wpt-pr: 32705
Automatic update from web-platform-tests
Re-add render-blocking WPT tests with memory-leaking tests removed
Currently, test_render_blocked_apis() causes a memory leak on Chrome if
the fullscreen-related test cases are run. The exact reason is still
under investigation.
To unblock the development of the render-blocking feature, this patch
disables the related test cases, and re-adds the previously remove WPT
test render-blocked-apis-by-stylesheed-link.tentative.html
Cq-Include-Trybots: luci.chromium.try:layout_test_leak_detection
Bug: 1293987, 1271296
Change-Id: I0e79fef97b5567322ec3e61446ef417fe3e9fe3a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3437423
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#967382}
--
wpt-commits: e0c27c6297f2aaa9b3378d9268d3162ad25b4b7f
wpt-pr: 32689
Automatic update from web-platform-tests
Support small/large/dynamic/logical viewport units
This CL adds support for new units:
* svw, svh (etc): Resolves against the viewport as it would be with
browser controls fully expanded.
* lvw, lvh (etc): Resolves against the viewport as it would be with
browser controls fully minimized.
* dvw, dvh (etc): Resolves against the viewport as it presently
appears given the current state of browser controls.
* vi, vb: Resolves against vw/vh depending on the writing-mode
of the target element.
Note that dv* units are deliberately not responsive to browser control
animations, and will always resolve to either sv* or lv* (not some
value in between). This is to avoid excessive scroll-driven relayouts
on mobile devices.
This CL uses the existing system/bits for invalidation of viewport
units. Targeted invalidation of dynamic units will come in a
subsequent CL.
Bug: 1093055
Change-Id: I3ba55a86de53514f2020a2d5bdda579f06dd9d0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3344791
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#967475}
--
wpt-commits: a78117ef25b74256ffc9850cd201fbed2117f3d5
wpt-pr: 32635
Automatic update from web-platform-tests
[BroadcastChannel] Add Partitioning WPT
This CL tests that BroadcastChannel is partitioned in third-party
contexts (tentative, pending changes to the spec).
For more info, see https://github.com/whatwg/html/issues/5803
Bug: 1239274
Change-Id: I8d495ecb141847276aefd1bcc4a1af0ea1098db2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3424369
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Andrew Williams <awillia@google.com>
Cr-Commit-Position: refs/heads/main@{#967421}
--
wpt-commits: 65d9fd570851f5446d6b1e3e6f07440f9b69a561
wpt-pr: 32690
Automatic update from web-platform-tests
Highlight API: Ignore CSS contain when painting
Per the CSSWG resolution [1], ignore CSS contain boundaries when
painting.
Update tests, and remove some tests that are no longer interesting
now that StaticRange painting no longer needs to take contain
boundaries into account.
[1] https://github.com/w3c/csswg-drafts/issues/4598
Bug: 1164461
Change-Id: Iad9249867ea704f924827db810816935069363c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3437210
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Fernando Fiori <ffiori@microsoft.com>
Commit-Queue: Dan Clark <daniec@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#967368}
--
wpt-commits: d6608a62788dd7c1595b73135d12fc6fb15f2b13
wpt-pr: 32688
Rodney Ding
Takahiro
moz-wptsync-bot
Hiroshige Hayashizaki
Blink WPT Bot
Scott Haseley
Peter Kotwicz
Jack Hsieh
Joonghun Park
Kent Tamura
Ben Kelly
Chris Lilley
Dan Sanders
msw@chromium.org
Anders Hartvoll Ruud
Rune Lillesveen
Findit
Morten Stenshorne
Oriol Brufau
Sam Weinig
Ms2ger
Anne van Kesteren
Johann Hofmann
Chris Dumez
Mike Bremford
Xiaocheng Hu
Andrew Williams
Dan Clark
Titouan Rigoudy