Automatic update from web-platform-tests
Never force a break before when we're already inside the node.
When resuming a node after a fragmentainer break, ignore break-before
values, since we're obviously not *before* it anymore (since we're
*inside*). We used to end up in an infinite loop, until out of memory,
not making any fragmentation progress. This was caused by monolithic
content, which, when printing, may take up space on subsequent pages.
This tricked us into thinking that it was a good place to insert a
forced break before the node we were resuming, since we were not at the
beginning of the page.
Bug: 1451760
Change-Id: I3c3168478f0f23035abd10597927cee47c00730c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4594563
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1156463}
--
wpt-commits: 880a978015c7284f469ceef183081e72932549ab
wpt-pr: 40493
Automatic update from web-platform-tests
Add WPTs for https upgrades and fallback
The upgrades test currently fails in Chromium since HTTPS upgrades are
implemented at the //chrome level and tests run in content shell, but
it was still considered useful to have WPTs to document the spec proposal.
These are being added as "tentative" since the https upgrades spec
change has not landed yet.
Bug: 1394910
Change-Id: Ie94f3421abc7e14a676fa06d3c9d1fdf572ee096
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4605846
Reviewed-by: Chris Thompson <cthomp@chromium.org>
Commit-Queue: Carlos IL <carlosil@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1156376}
--
wpt-commits: 7c5bebb89c041d4be30168a88e60deda08ed4bb2
wpt-pr: 40506
Automatic update from web-platform-tests
HTML: Add <source media> to media elements
See https://github.com/whatwg/html/pull/9341
--
wpt-commits: 0f4b390234ab06f8841c9e89c74afc04c66c7f91
wpt-pr: 40330
Automatic update from web-platform-tests
Layout 2020: Properly handle negative block margins in floats
If a float has negative block margins, it should be pushed upward, but
shouldn't affect the positioning of any floats that came before it. It
should lower the ceiling though when it still has some non-negative
block contribution. In order to implement this behavior, we should only
place the float considering its non-negative block length contribution. If
the float is pushed up completely past it's "natural" position, it
should be placed like a float with zero block size.
--
wpt-commits: 67a14f64b7b481a3c6956f8bee2af331029bb1c7
wpt-pr: 40471
Automatic update from web-platform-tests
Add a WPT for touch-action behavior with swipe direction changes.
This test covers the following issue for PointerEvents v3:
https://github.com/w3c/pointerevents/issues/303
Change-Id: I37d174f86ea5dbe907655c88d787461f9fda7174
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4602384
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1155765}
--
wpt-commits: bfa0d9f154f70c70f076ac756cb1486301983e50
wpt-pr: 40464
Automatic update from web-platform-tests
[anchor-position] Parse and evaluator `auto` and `auto-size` keywords
This patch adds two more anchor side keywords `auto` and `auto-size`
to the `anchor()` function, and evaluates them by converting them into
the corresponding physical sides.
This patch doesn't implement the automatic fallbacks, which will be
implemented by a follow-up patch.
Spec: https://drafts.csswg.org/css-anchor-position-1/#anchor-auto
Bug: 1412864
Change-Id: I0494ab943a07ab9916b430600d4f49235c5df084
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4602508
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1155689}
--
wpt-commits: 11ff902e0691e9ed7d659bd7bba02eabdb9949d2
wpt-pr: 40463
Automatic update from web-platform-tests
[RemoveLegacy] GridTrackList::legacy_track_list_
This wasn't used anymore. This fixes an OOM we had which trying
parse many repeated tracks.
There should be no behaviour change.
Bug: 1229581
Fixed: 1350760
Fixed: 1214890
Change-Id: I0e3463018473689c6d9274907e4c024a6dc14a5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4599018
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1155596}
--
wpt-commits: d323512bb2ac0204659295a575169562b3799a11
wpt-pr: 40475
Automatic update from web-platform-tests
MediaRecorder: Don't throw with video mimeType for audio-only stream
This CL makes sure MediaRecorder start() does not throw if video
mimetype is supported for audio-only streams.
Bug: 1451036
Change-Id: I5388ba8d67d20ae1857933fcd574653cf3e9589e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4584893
Reviewed-by: Markus Handell <handellm@google.com>
Commit-Queue: Fr <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/main@{#1155443}
--
wpt-commits: b152a5ac31a97d46daf2eca770a23e532fa06b0f
wpt-pr: 40379
Automatic update from web-platform-tests
[css-flex] Try a more conservative intrinsic sizing algorithm
Our first attempt at a better algorithm was not compatible with the web.
This version gives behavior closer to what is currently shipping in all
browsers.
The difference in this version affects only single-line row containers'
min-content sizes. For such containers where no items are growing from
their flex basis to their desired min contribution, an item's final
contribution to the container's min-content size is (1) its flex-basis
if the item has a 0 flex factor in whichever direction it wants to go
(shrink if flex-basis > min-content contribution, grow otherwise);
otherwise: (2) its min-content contribution.
This will probably only be enabled for a few days, but will give us good
compat data even so.
Bug: 240765
Change-Id: Ib8ae101ec88b4f0e543c8f4ecb713edb68074cb4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4602419
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1155331}
--
wpt-commits: d8c97e60188a11882d3222f181fb536b9e173393
wpt-pr: 40466
Automatic update from web-platform-tests
Reland "Fenced frames: Local network access."
This is a reland of commit c02af164b8b7cee63e3c97901113c386f9100e67
Previous submit caused test timeout for the two new tests:
1. fenced-frame-subresource-fetch.tentative.https.window.js
2. fenced-frame.tentative.https.window.js
For fenced frames, we obtain messages by writing value to/reading
value from a server. This is significantly slower than similar tests
using iframes, because iframes can simply use `window.postMessage()`.
I've specified long timeout for both tests by `// META: timeout=long`.
Otherwise this CL is the same as the original one.
Original change's description:
> Fenced frames: Local network access.
>
> Fenced frames are only allowed in secure context. So the tests are
> all in secure contexts.
>
> 1. Subresource fetch:
>
> Fenced frame's IP address space is set to `kPublic` in order to make
> it subject to local network access check.
>
> web_tests/external/wpt/fetch/local-network-access/
> fetch.https.window.js is replicated and replaced iframes with fenced
> frames. All test cases are passing with the same behaviors as iframes.
>
> 2. Document fetch:
>
> Fenced frame's document fetch initiator can only be the parent.
> Fenced frames can only be navigated in two ways:
>
> 1. Directly by their parent, and never by another frame at a distance
> via `window.location` or `window.open`; in this case the `ClientSecurityState` needs to come from the parent.
> 2. By themselves; in this case the `ClientSecurityState` also needs to
> come from its embedder/parent.
>
> The ClientSecurityState of its parent is supplied to the
> NavigationURLLoader.
>
> web_tests/external/wpt/fetch/local-network-access/
> iframe.tentative.https.window.js is replicated and replaced iframes
> with fenced frames. All test cases have the same results as the
> iframe test expectations, except one:
>
> treat-as-public-address to local (same-origin): no preflight
> required
>
> - Iframe: the request is made without preflight. The nested iframe is
> loaded successfully.
>
> - Fenced frame: a preflight is made, and gets blocked. See a. below.
>
> I changed the test expectation for this test only. (PASS for iframe,
> but FAIL for fenced frame)
>
> Here are some noteworthy things we observed for document fetch. The
> following only applies to embedder-initiated navigations (i.e., the
> initial navigation of the frame):
> a. Fenced frame's document fetch's preflight request is always sent
> with `Origin: null`. This applies to embedder-initiated navigations
> (i.e., the initial navigation of the frame). I think this affects the
> outcome of Local Network Access check algorithm.
> https://source.chromium.org/chromium/chromium/src/+/main:content/browser/fenced_frame/fenced_frame.cc;l=119-126?q=fencedframe::n&ss=chromium%2Fchromium%2Fsrc
>
> A `null` origin implies
> LocalNetworkAccessChecker::is_potentially_trustworthy_same_origin_
> will always be false.
>
> b. For testing purposes, we tried manually overriding the initiator
> origin with a real origin and found that the preflight request still
> failed. This is because the credentials mode of the navigation is
> `'include'`, which prevents `Access-Control-Allow-Origin: '*'` from
> working, which iframes equivalently suffer from: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/fetch/local-network-access/iframe.tentative.https.window-expected.txt?q=%22FAIL%20%22%20f:third_party%2Fblink%2Fweb_tests%2Fexternal%2Fwpt%2Ffetch%2Flocal-network-access%2Fiframe.tentative.https.window-expected.txt.
>
> Bug: 1420626
> Change-Id: I74c97369d235e1725c650bfe87f29372992cb56b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4532557
> Reviewed-by: Titouan Rigoudy <titouan@chromium.org>
> Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
> Reviewed-by: Weizhong Xia <weizhong@google.com>
> Commit-Queue: Xiaochen Zhou <xiaochenzh@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1154027}
Bug: 1420626, 1451954
Change-Id: I5c1f326e991f14125f5c3991046553d6e3200784
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4595521
Reviewed-by: Titouan Rigoudy <titouan@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Weizhong Xia <weizhong@google.com>
Commit-Queue: Xiaochen Zhou <xiaochenzh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1155231}
--
wpt-commits: 4a3bd0bbe8a888504b287ef46759c31fd121f64b
wpt-pr: 40410
Automatic update from web-platform-tests
Fix captureTime verification timeouts
Verifying that `captureTime` is present in VideoFrameMetadata is not
possible. For local streams, it can take an undetermined amount of time
for the field to start appearing, and tests can still fail when they
are tagged as long-running (60s).
This CL removes `captureTime` verifications and re-enables disabled
WebRTC + video.requestVideoFrameCallback WPT tests.
Fixed: 1377004
Change-Id: Iba92b529dffe67d32831bfafd81f02a114676b43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4602386
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Auto-Submit: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1155179}
--
wpt-commits: 09f32d87cded8a1e4a6cbb7cf64cea9e6239dcca
wpt-pr: 40465
Automatic update from web-platform-tests
[image-set] Fix expectation of image-set with calc().
This fixes some of the tests introduced in
ba004353155163b0c356b753394e50d2dd6f0b87.
Resolutions like any other calc()-supporting dimensions are specified to
simplify as much as possible, and serialize to the canonical units.
This is what css-values-4 specifies, and there are other tests in this
file which already have that expectation.
--
wpt-commits: 7cd551100fa719c750ead588f02a5fabc0b3a501
wpt-pr: 40461
Automatic update from web-platform-tests
Fix scrollbar-width repaint issues on non viewports
This patch fixes issues with dynamically switching between
scrollbar-width values.
Previously the ScrollbarWidth check would prevent
SetScrollbarNeedsPaintInvalidation from being called.
ScrollbarWidth is still checked for none values inside
ComputeScrollbarExistence and ScrollbarTheme implementations.
Only viewport level changes are still broken.
WPT tests included
Change-Id: I606e3ba7cecca160045af70f42cfea0567370216
Bug: 891944
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4567548
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1155115}
--
wpt-commits: a73e0d1ef317d164c58e51cd82006e9684649932
wpt-pr: 40324
Automatic update from web-platform-tests
[FedCM] Move getUserInfo() tests to its own file
This CL moves existing getUserInfo() tests to a separate file, which
lets us not have too many tests in the same file and show coverage for
the feature more easily.
Change-Id: Ib83099ad3cce4aae971b746a087ddec682efe79b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4600295
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Nicolás Peña <npm@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1155048}
--
wpt-commits: 0ef2754742e5e22a2f8926f526ecb1d0fa6cec34
wpt-pr: 40455
Automatic update from web-platform-tests
Shared Storage: Make internal web tests external
We move the shared storage WPT from wpt_internal/ to external/wpt/ and
update file-path URLs in them as necessary.
Bug: 1451968,1218540
Change-Id: Ibdf33bbd9b53036e40347f9e6398b73a5860953b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4594158
Commit-Queue: Cammie Smith Barnes <cammie@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Yao Xiao <yaoxia@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1154946}
--
wpt-commits: c2ec4c5131d43e0a8b141afa5acbd5bd36181341
wpt-pr: 40427
Automatic update from web-platform-tests
sensors: Reset sensor state on context destruction.
Sensor::ContextDestroyed() did not reset |state_|, which could lead to a
crash in SensorProxyImpl::RemoveActiveFrequency() if Sensor::stop()
ended up being invoked later (e.g. via a reference to an object created
in an iframe).
Fixed: 1453186
Change-Id: I14d58f012af300631f43494b2d8a75fc0ca52562
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4595840
Auto-Submit: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1154979}
--
wpt-commits: 99f37e54b8b701acb046904a11a987fe6b0a84bd
wpt-pr: 40415
Automatic update from web-platform-tests
Expose AbsCaptureTime on RTCEncodedAudioFrameMetadata
Exposing this attribute behind a flag allows us to compare two
RTCEncodedAudioFrames in case they had the same producer.
The AbsCaptureTime extension is defined here: https://webrtc.googlesource.com/src/+/refs/heads/main/docs/native-code/rtp-hdrext/abs-capture-time
Change-Id: I997373dc939b3b25258eb9b508fdc0de773808c0
Bug: webrtc:15220
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4584627
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Palak Agarwal <agpalak@chromium.org>
Reviewed-by: Tony Herre <toprice@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1154938}
--
wpt-commits: 53963cd381d8328ff62b7bf71ebdcf73f3107aba
wpt-pr: 40359
Automatic update from web-platform-tests
Add an automated WPT for PointerEvents getPredictedEvents.
This test covers the following PR to the PointerEvents spec:
https://github.com/w3c/pointerevents/pull/382
Change-Id: I7f7b6fee2b8e9e866e8bdff86ef8becb41547b65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4591589
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Auto-Submit: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1154899}
--
wpt-commits: 75039e99016ae64d3d23fac2bba3120a5da5b2f2
wpt-pr: 40386
Automatic update from web-platform-tests
Add test for paragraph and line separators (#40364)
* Add test for paragraph and line separators
--
wpt-commits: d9b66ad41d30a463ec1a17dc7be67b8fe8944478
wpt-pr: 40364
Automatic update from web-platform-tests
Don't make WebDriverExceptions force-fail the test (#40058)
Instead, allow JavaScript to catch them, and have the `unhandledrejection`
handler trigger the test failure if they are not caught.
Fixes#40057
--
wpt-commits: 15522c48a8938ca569640ee5874f013e404b8f90
wpt-pr: 40058
Also fixes author information for patch:
"Bug 1654112 - Tweak upstream gn files for Firefox build."
This patch had, probably due to previous history editing,
been changed from Dan Minor to stransky. Now it is
correct, showing Dan Minor as the author.
Differential Revision: https://phabricator.services.mozilla.com/D181582
Morten Stenshorne
moz-wptsync-bot
Carlos IL
Darin Adler
Simon Pieters
Martin Robinson
Tim Nguyen
Mason Freed
Mustaq Ahmed
Xiaocheng Hu
Ian Kilpatrick
dependabot[bot]
François Beaufort
David Grogan
Xiaochen Zhou
Thomas Guilbert
Emilio Cobos Álvarez
Daniil Sakhapov
Luke Warlow
Keith Cirkel
Nicolás Peña
Camillia Smith Barnes
Raphael Kubo da Costa
Aaron Leventhal
Palak Agarwal
Anne van Kesteren
Munira
Rakina Zata Amni
Christian Biesinger
ganna
Michael Froman