Automatic update from web-platform-tests
Fetch (CORS): Range header with HTTP OWS results in preflight
--
wpt-commits: 62897e77269c2b64291d485f0841de770feed25d
wpt-pr: 37569
Automatic update from web-platform-tests
[IdleDetection] Move page visibility test from wpt_internal to external/wpt
The page visibility test does not become a wpt before because there
is no infrastructure for simulating loss of visibility. This CL makes
the test become a wpt by simulating loss of visibility through
minimizing the window.
Bug: none
Change-Id: Iae8c2ec15d8030fc4f76337b5d8a344d073324a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262544
Commit-Queue: Wei4 Wang <wei4.wang@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1107303}
--
wpt-commits: d963c44ccce62d04bb7ab931464913665508d2b3
wpt-pr: 38564
Automatic update from web-platform-tests
Add test for preserve-3d, with a transformed pseduo element.
--
wpt-commits: 49819d78d44b87d5ebb076c5b005dcbfc630c24f
wpt-pr: 38505
Automatic update from web-platform-tests
URL: fix invalid IPv6 test
This test was introduced in https://github.com/web-platform-tests/wpt/pull/38484.
The result of test with input "http://[::127.0.0.1.]" must be failure, as the IPv6 parser returns failure in step 6.5.5.2.2 when numbersSeen becomes 4.
--
wpt-commits: 96ef5777e50f7ed8f54b91525002d6708fc097d7
wpt-pr: 38573
Automatic update from web-platform-tests
URL: correct location.href failure tests
Tests depended on results of prior tests and the tested exception was incorrect per the HTML Standard.
--
wpt-commits: 5ff3ad864bcf03509806e1feeb3bc208f9ffae1f
wpt-pr: 38581
Automatic update from web-platform-tests
Add links to landed popover spec, update explainer link
No functional change here. This just updates the link for the
explainer from `popup` to `popover`, and adds a link to the
landed spec.
Bug: 1307772
Change-Id: Ie549e56d86125c8cf1ab3ac790a6f55867d5810d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265463
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Di Zhang <dizhangg@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Commit-Queue: Di Zhang <dizhangg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1107097}
--
wpt-commits: 45fdf45f79582953fb3aa708566cd2c0707cb222
wpt-pr: 38578
Automatic update from web-platform-tests
Revert "Make inferred roles for CSS toggles influence accessibility role."
This reverts commit 23486a5ee14f6d10a7df673c124eaf1759ab22e4.
Reason for revert: Part 2 of reverting the two chained CLs, part one is crrev.com/c/4265141. Started causing a consistent failure on Win10 Tests x64. Example can be seen here: https://ci.chromium.org/ui/p/chromium/builders/ci/Win10%20Tests%20x64/77339/overview
Original change's description:
> Make inferred roles for CSS toggles influence accessibility role.
>
> The tests added in this CL are mostly testing the inference engine added
> in the previous CL.
>
> Support for toggles is controlled by the CSSToggles flag (currently off)
> in RuntimeEnabledFeatures.
>
> Bug: 1250716
> Change-Id: Ia0b38b5c7ffacc4d2a6eec88ecfe0ada852c4b09
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4200858
> Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
> Commit-Queue: David Baron <dbaron@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1106967}
Bug: 1250716
Change-Id: If047c87563e9fe6e90a5a9d411762fb6cba16fd4
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265140
Commit-Queue: Tim <tjudkins@chromium.org>
Owners-Override: Tim Judkins <tjudkins@google.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1107091}
--
wpt-commits: 7093c905a52c21ecf331b4ad08cdf65ad10ad027
wpt-pr: 38579
Automatic update from web-platform-tests
[Private Network Access] Test insecure fetches within workers loaded from blob urls
Workers can be loaded from a blob URL. This CL adds a test that tests
Private Network fetches within such workers.
This test will also be useful when we start allowing same origin PNA
requests. We don't currently have a working same-origin tests about
fetches in dedicated workers. The current treat-as-public-address tests
don't work well because dedicated workers don't get their policies from
network headers when PlzDedicatedWorker is disabled.
Bug: 1382068
Change-Id: I483575eece53e7232ce0baae308f147b1ab65b46
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250757
Commit-Queue: Jonathan Hao <phao@chromium.org>
Reviewed-by: Yifan Luo <lyf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1105696}
--
wpt-commits: 5e38a4d8860cbdcd78283bbb58e2515d53487fbb
wpt-pr: 38495
Automatic update from web-platform-tests
Make inferred roles for CSS toggles influence accessibility role.
The tests added in this CL are mostly testing the inference engine added
in the previous CL.
Support for toggles is controlled by the CSSToggles flag (currently off)
in RuntimeEnabledFeatures.
Bug: 1250716
Change-Id: Ia0b38b5c7ffacc4d2a6eec88ecfe0ada852c4b09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4200858
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106967}
--
wpt-commits: 148d52e548f3971fa7666f84997afeacecc16e8c
wpt-pr: 38395
Automatic update from web-platform-tests
:fullscreen should match all elements with the fullscreen flag set
Adding new elements to the top layer for fullscreen does not remove
the existing fullscreen'ed elements from the top layer and the
fullscreen is not reset either. Make sure all fullscreen'ed elements
match the :fullscreen pseudo class.
Bug: 938287
Change-Id: I70dfc88d1d76912a61c4a2563e96fb4404dd8dd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261172
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106929}
--
wpt-commits: b1011dff8e6ebce960f25ab82eef7dd14baecedd
wpt-pr: 38560
Automatic update from web-platform-tests
Add a test for sticky position with fractional offsets
When a sticky positioned element has a fractional offset, a 1px gap
should not bleed through.
Bug: 1136079
Change-Id: I37aaa399529d1c4bf82a33b33bb0e491ec8cfca3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262133
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106913}
--
wpt-commits: b07ae5f7cf257ecd6738df267f6652ea6b54003b
wpt-pr: 38570
Automatic update from web-platform-tests
Allow the navigate event to cancel same-document main-frame traversals
Currently, the navigate event is allowed to cancel push/replace/reload
navigations, but not traversals. There are two reasons for this:
chromium's architecture made it difficult to support cancelation
without getting out of sync with the authoritative version of the
joint session history in the browser process, and we were
concerned about the possibility of trapping the user if canceling
a traversal was too easy.
The case where we might get out of sync is when multiple frames
navigate as part of a traversal. We want to avoid the case where
some frames cancel the navigation in their frame, but others allow
it to proceed (since giving every frame what it requested would
cause some frames to be out of sync with the browser process). Therefore, only the main frame is allowed to cancel the navigation
via the navigate event. In order to ensure the main frame is able to
cancel the entire traversal, we send the main frame navigation (if any)
to the renderer first and wait for its commit to complete before
proceeding with any subframe navigations.
The main frame is only allowed to cancel a traversal when it is
traversing same-document (regardless of whether its subframes
traverse same-document or cross-document). We had originally
planned on allowing cross-document traversals to be cancelled, too
(https://chromium-review.googlesource.com/c/chromium/src/+/3868615),
but this proved to have unacceptable performance characteristics,
requiring roundtrips to the renderer whenever a navigate event
handler was present, even if the navigate event handler had no
intention of ever cancelling a traversal.
Therefore the sequence during a traversal is now:
1. Calculate which frames to navigate, and invoke
Navigator::Navigate() for each.
2. The main frame's NavigationRequest will proceed as normal.
3. If the main frame needs to do a same-document navigation, then:
3a. Any subframe navigations will be deferred until the main
frame NavigationRequest either commits or is canceled.
3b. If it cancels, abort the entire traversal.
3c. Resume all deferred subframes. These navigations will all fire
a navigate event just before committing, but none of those of
those events will be cancelable.
As for preventing trapping the user, we only allow canceling the
navigation in the main frame if the navigating is programmatic, or
if there is a consumable user activation. This ensures that, e.g.,
pressing the back button once might be canceled by the navigate
event, but the second back button press is guaranteed to go through.
Traversals via the navigation API or the legacy history API will
always be cancelable because they are programmatic. Canceling a
traversal consumes HistoryUserActivationState rather than
UserActivationState, in order to minimize the potential for
collisions with other UserActivationState consumers that are not
in the history/navigation space.
Bug: 1371580
Change-Id: I0c8c39bec8e21f3ca86389a4343881ebe2bde43e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4092862
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106877}
--
wpt-commits: 58d0f1accd7694d19a5fa71661aec8aec90b6d68
wpt-pr: 37460
Automatic update from web-platform-tests
Make IPv6-embedded IPv4 addresses parse only if they have 4 parts (#38484)
The URL standard requires the IPv6-embedded IPv4 address to be consicely
composed of 4 parts. A check is added in the URL host parser to fix the
WPT test failures.
The feature is implemented behind the StrictIPv6EmbeddedIPv4AddressParsing flag.
Bug: 1411619
Change-Id: I9062aef7279b899db961613b6e42f6095d2101d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4206417
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Jiacheng Guo <gjc@google.com>
Reviewed-by: Weizhong Xia <weizhong@google.com>
Cr-Commit-Position: refs/heads/main@{#1106646}
Co-authored-by: Jiacheng Guo <gjc@chromium.org>
--
wpt-commits: ff3fad2e4368f66cd9a26f2836120f4f7a98b3e1
wpt-pr: 38484
Automatic update from web-platform-tests
Pre-paint: Only walk child views when at the first fragment.
We only paint/hit-test the first fragment of monolithic nodes that just
support one fragment. Monolithic nodes usually don't generate multiple
fragments, but this may happen if the content is inside a repeated table
section or fixed positioned element. Skip the other fragments, just like
we do during painting and hit-testing. Otherwise we might end up setting
paint offsets relatively to the wrong fragment in the parent document.
This was also problem when repeating content inside multicol, although
it was failing a bit more flakily there.
Bug: 1414873
Change-Id: I3e12c6a3a97d51c2dfe6de1f72ae6726ae11fc91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264149
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106850}
--
wpt-commits: 9ec82ce75e8339e34d1fa7625a83baf648c9c6d9
wpt-pr: 38566
Automatic update from web-platform-tests
vt: iframe scrollbars paint last during transition
In a main frame, scrollbars paint during the kOverlayOverflowControls
phase while in an iframe they paint during kSelfBlockBackgroundOnly. The
former causes the scrollbars to avoid being part of the root snapshot
due to the way we handled https://crbug.com/1303081. The latter causes
the scrollbar to be painted into the iframe's root snapshot which is
unintended.
This CL changes the paint order of iframe scrollbars to match the main
frame since iframes also cannot have content that paints over top of
a scrollbar.
Bug: 1407299
Change-Id: Ida74507e59b16f64134807ed56487fc6fb569e1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4241484
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106800}
--
wpt-commits: 8aa97ba28e1c4fa92bedbb5c7635efb2bcc10fce
wpt-pr: 38499
Automatic update from web-platform-tests
Add test for BYOB reader for Blob.stream() (#37925)
--
wpt-commits: c9a3667cce44ac9b7a8f1dbe91b78ed846426c65
wpt-pr: 37925
Automatic update from web-platform-tests
[wasm] Exception -> Tag in basic.tentative.any.js
This need to change in order to work with #38549, which merged
WebAssembly/exception-handling#252.
--
wpt-commits: cde25e7e3c3b9d2280eb088a3fb9da988793d255
wpt-pr: 38561
Automatic update from web-platform-tests
Prerender: add WPT for main frame navigation in a prerendered page
This CL adds a web platform test to check if document.prerendering and prerenderingchange event in the navigated page.
Bug: 1239281
Change-Id: I22f80c67be228c092c141e8e4a29de8e8b86ceba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4229457
Reviewed-by: Koji Ishii <kojii@chromium.org>
Auto-Submit: Asami Doi <asamidoi@chromium.org>
Reviewed-by: Huanpo Lin <robertlin@chromium.org>
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106657}
--
wpt-commits: 27bfcca6ce44874880c9628b93f8891053d2ea56
wpt-pr: 38483
Automatic update from web-platform-tests
usb: Use Mojo union to separate device open success from error codes
Mojo doesn't support a void type (issue 1220106) but we can emulate one
with an enum that has only one defined value. This change adds a new
UsbOpenDeviceResult union which is either a UsbOpenDeviceSuccess or a
UsbOpenDeviceError.
Change-Id: If158c1dd52315fd1bf51062a4b8e64a3ed967a84
Bug: None
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4234077
Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1105463}
--
wpt-commits: 66933c819b6e399f2444356b3e111e291d328e52
wpt-pr: 38504
Automatic update from web-platform-tests
Reland "Reland "Generate canvas layer global state tests with new test variants feature.""
This is a reland of commit 0511f163d2d9ccba4a98deab26972b46f5f2d05e
Original change's description:
> Reland "Generate canvas layer global state tests with new test variants feature."
>
> This is a reland of commit 446ce8aea96e6d4696d9702c1ac86861c9c8cdf6,
> with pixel fuzzy tolerance updated to account for the mac11-arm64-rel
> builder.
>
> Original change's description:
> > Generate canvas layer global state tests with new test variants feature.
> >
> > All of these tests were very similar with the only important different
> > being the global state applied in the setup. Adding a "variant" feature
> > to the test generation script allows for cutting a lot of this
> > repetitive code.
> >
> > Change-Id: Ic3ac63e80ff9c5290ae5f98a29c7d854951e9ba7
> > Bug: 1409873
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209308
> > Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
> > Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
> > Cr-Commit-Position: refs/heads/main@{#1105685}
>
> Bug: 1409873
> Change-Id: I21eeeb2b1581097d37eaaa3fd41da159ffb02e0f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255729
> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
> Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1106242}
Bug: 1409873
Change-Id: Iddd1e1e90adb24f03f019a9839a7559412bf2f77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262432
Reviewed-by: Jeffrey Cohen <jeffreycohen@chromium.org>
Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106497}
--
wpt-commits: bcf4a27c0a9dbb07d974a880acb26eb289a85c7e
wpt-pr: 38556
Automatic update from web-platform-tests
vt: Compute size for inline elements
Inline elements were failing to perform a transition as their size and
visual overflow rects weren't being computed and set to default empty
values.
This CL adds a case for inlines using the border bounding box rect.
Bug: 1415356
Change-Id: Iaf5ab9ede57601b2e4ab53cf348622b9a7e45c95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4252539
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106367}
--
wpt-commits: 0bfac4cb1a1b204901c92e46d78c13595ad84248
wpt-pr: 38542
Automatic update from web-platform-tests
Revert "Reland "Generate canvas layer global state tests with new test variants feature.""
This reverts commit 0511f163d2d9ccba4a98deab26972b46f5f2d05e.
Reason for revert: Failing windows tests here https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Win10
Original change's description:
> Reland "Generate canvas layer global state tests with new test variants feature."
>
> This is a reland of commit 446ce8aea96e6d4696d9702c1ac86861c9c8cdf6,
> with pixel fuzzy tolerance updated to account for the mac11-arm64-rel
> builder.
>
> Original change's description:
> > Generate canvas layer global state tests with new test variants feature.
> >
> > All of these tests were very similar with the only important different
> > being the global state applied in the setup. Adding a "variant" feature
> > to the test generation script allows for cutting a lot of this
> > repetitive code.
> >
> > Change-Id: Ic3ac63e80ff9c5290ae5f98a29c7d854951e9ba7
> > Bug: 1409873
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209308
> > Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
> > Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
> > Cr-Commit-Position: refs/heads/main@{#1105685}
>
> Bug: 1409873
> Change-Id: I21eeeb2b1581097d37eaaa3fd41da159ffb02e0f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255729
> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
> Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1106242}
Bug: 1409873
Change-Id: I93c6c95354fc78d74876750a5924134d0daab1be
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260694
Auto-Submit: Jeffrey Cohen <jeffreycohen@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1106352}
--
wpt-commits: 40bafce0240d329546e14e72fcd08e7b14e91a61
wpt-pr: 38554
Automatic update from web-platform-tests
Reland "Generate canvas layer global state tests with new test variants feature."
This is a reland of commit 446ce8aea96e6d4696d9702c1ac86861c9c8cdf6,
with pixel fuzzy tolerance updated to account for the mac11-arm64-rel
builder.
Original change's description:
> Generate canvas layer global state tests with new test variants feature.
>
> All of these tests were very similar with the only important different
> being the global state applied in the setup. Adding a "variant" feature
> to the test generation script allows for cutting a lot of this
> repetitive code.
>
> Change-Id: Ic3ac63e80ff9c5290ae5f98a29c7d854951e9ba7
> Bug: 1409873
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209308
> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
> Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1105685}
Bug: 1409873
Change-Id: I21eeeb2b1581097d37eaaa3fd41da159ffb02e0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255729
Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106242}
--
wpt-commits: 27ae5af35c48530aca3ba94823eafc570a2704bd
wpt-pr: 38534
Automatic update from web-platform-tests
vt: Fix minor test bugs
A few tests are still using `view-transition-container` which has been
renamed to `view-transition-group`.
There's also a few tests which were accidentally assigning the result of
requestAnimationFrame to `onload`, rather than calling it from the load
event.
Change-Id: I9d11aca52aeefbe72429f545db283967ecb9e824
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257226
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Auto-Submit: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1106218}
--
wpt-commits: 35dc699ace05ab06163ece7c77fa368b293b47c0
wpt-pr: 38535
