Automatic update from web-platform-tests
Re-land pull_request_previews.yml workflow (#21558)
This attempts to re-land the pull_request_previews.yml workflow, to
create deployments for wptpr.live. This was previously reverted because
it was not properly triggering the dependent deployment workflow. I've
tested it on my local fork of wpt with my personal token and can't
reproduce the failure (i.e. it is working), so I'm landing this again to
see if it works now.
This reverts commit 462f3c4680dc9d4c5dd4740742947cd16d6fc1df. I've
changed two main things:
* Use my personal token temporarily, to mimic the local setup.
* Only deploy one PR, to avoid spamming.
--
wpt-commits: 5bfe66a9068ede4f0228ace529c3bc7b1a54c202
wpt-pr: 21558
Automatic update from web-platform-tests
Update chromium log formatter to handle known_intermittent. (#21517)
Update chromium log formatter to handle known_intermittent.
It will combine the expected status and anything in known_intermittent
into a space-separated list of statuses which are output into the
"expected" field in the chromium log.
--
wpt-commits: 9a559c43f8c4469af284d460f89b295eae4edc9b
wpt-pr: 21517
Automatic update from web-platform-tests
Remove instance of 'whitelist' in css/css-pseudo
As per https://whatwg.org/style-guide
--
wpt-commits: 1703644cf1da595b6926d1f6007c17121720a5b3
wpt-pr: 21319
Automatic update from web-platform-tests
[Security] Fix WPTs that are wrong or with undeterministic failure output
This fixes three tests:
- blob-popup.https.html checked for a random string to be empty,
which makes test expectations unreliable, use length instead.
- coop-navigated-popup.https.html had a failure in the cleanup, trying
to use a non-existent object. This change defines the broadcast channel
beforehand and uses the proper variable name.
- historical/coep-navigate-popup-unsafe-inherit.https.html had an
invalid expectation that navigating a popup from a COOP: same-origin
document to a COOP: unsafe-none document should not create a new
browsing context group.
Bug: 922191
Change-Id: Ife24aee4369a3a25bbff32a2fe5e8c29abb2d468
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030902
Commit-Queue: Pâris Meuleman <pmeuleman@chromium.org>
Auto-Submit: Pâris Meuleman <pmeuleman@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Arthur Hemery <ahemery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737734}
--
wpt-commits: b49a11955de10ebff809462df4b54d5609b41fb9
wpt-pr: 21547
Automatic update from web-platform-tests
Block the XML parser on parser blocking stylesheets.
The html spec talks about script blocking stylesheets[1], but we do
script blocking in body by pausing the html parser. The APIs for doing
that for the XML parser had empty implementations which meant that
querying style from a script after an external stylesheet resource would
not wait for the stylesheet to load.
[1] https://html.spec.whatwg.org/multipage/semantics.html#interactions-of-styling-and-scripting
Bug: 1043944, 917116
Change-Id: I08422fa0608db8972154a8b19854906e154dfdd2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012021
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737721}
--
wpt-commits: 220c6b1d4bd084c1835cf274f3ed5f8dd8468fea
wpt-pr: 21335
Automatic update from web-platform-tests
[css-pseudo] Fix hit-testing for nested ::marker
Since r731964, if you clicked a ::marker originated by a ::before or
::after, and you read the 'path' property of the event, the first node
in the array might be the ::before or ::after pseudo-element.
Actually it was fine if you clicked the contents (text or image) of the
::marker. But it's possible to make the ::marker taller than its
contents by setting a big 'line-height'. Then you could click inside the
::marker but outside its contents, and reproduce the problem.
That was wrong, as described in pseudo_element.h,
> Pseudo element are not allowed to be the inner node for hit testing.
This patch fixes it by making PseudoElement::InnerNodeForHitTesting
iterate ancestors until it finds one which is not a pseudo-element.
Bug: 1048000, 457718
TEST=external/wpt/css/css-pseudo/marker-hit-testing.html
Some checks fail in legacy because the marker ignores 'line-height'.
Change-Id: I7bed7d0824638b0c7f4b63a744a3ca4978285445
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030973
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#737720}
--
wpt-commits: 738d7d25a53e359ecb83349885a34a61b3944fa5
wpt-pr: 21542
Automatic update from web-platform-tests
IndexedDB: Drop max numbers in parallel-cursors-upgrade.html
The external/wpt/IndexedDB/parallel-cursors-upgrade.html test
exercises 10k cursors in parallel, which an implementation should
support. The test was historically flaky, although it hasn't timed out
on the bots lately. But it is still slow - requiring multiple seconds
on many platforms, and 20-40 seconds on debug builds. Drop the maximum
number of parallel cursors to stop being such a drain on the commons.
Local tests: the time for --iterations=40 dropped from 23s to 5s.
Bug: 869364
Change-Id: I5a0b9de3b37650917e40cc0c34e7473a3870b21f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033814
Auto-Submit: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737669}
--
wpt-commits: 3487b250cd7304e7c8e6e7c447a8e3aee2c22082
wpt-pr: 21536
Automatic update from web-platform-tests
Move tests in custom-elements/state/ to external/wpt/custom-elements/state.tentative/
Rename |internals| to |i| to avoid lint errors.
This is a preparation to ship the feature.
Bug: 1012098
Change-Id: I789f44c072b57f05e1ec8ddfbf0855872e144996
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032632
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737659}
--
wpt-commits: 7b464208c72a8cf11236204b7af4bf17170ebe42
wpt-pr: 21541
Automatic update from web-platform-tests
Add some tests for Node IDL members on Attr objects
--
wpt-commits: 70490abb43593ab54c736e2fb6b5dc1cd3b306c0
wpt-pr: 21540
Automatic update from web-platform-tests
Add WPT tests to verify pings do not send a referrer header
Add WPT tests to verify pings do not send a referrer header as
specified in step 3:
https://html.spec.whatwg.org/multipage/links.html#hyperlink-auditing
Bug: 1046392
Change-Id: Ie0f133be6db34084aac26280a29a90cc9e68e707
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024855
Reviewed-by: Dominic Farolino <dom@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Rob Buis <rbuis@igalia.com>
Cr-Commit-Position: refs/heads/master@{#737596}
--
wpt-commits: c67d8f5bdace9762af3ea99417fb5f2140438e14
wpt-pr: 21469
Automatic update from web-platform-tests
[css-flex] More changes to test suite after review of files (#7947)
* Made more changes based on analysis of tests that were <= 5 tests to a given url hash in flex
* Restore assert
Co-authored-by: Greg Whitworth <865244+gregwhitworth@users.noreply.github.com>
Co-authored-by: Stephen McGruer <stephen.mcgruer@gmail.com>
--
wpt-commits: 81a0e680add2d790bc8e0473c2b9407855703b40
wpt-pr: 7947
Automatic update from web-platform-tests
Major new manifest version (v8): path trie edition
This essentially implements https://github.com/web-platform-tests/rfcs/pull/40.
--
wpt-commits: 31c0f5efba38b7d1d7f45ac449bcbc892e8771ce
wpt-pr: 16537
Automatic update from web-platform-tests
[ElementTiming and LargestContentfulPaint]Fix background img sizes
Currently, we use exclusively the size of the LayoutObject to compute
the background image sizes. This is incorrect, for instance when looking
at CSS styles like ::first-letter. This CL fixes this by passing the
image border to ImagePaintTimingDetector and ImageElementTiming.
Bug: 996921
Change-Id: I94e4a2f3c8873be765b144179f7729430c885dac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023523
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737289}
--
wpt-commits: 3061f228d3d8b900b3aec8c7642ff58fc04ea011
wpt-pr: 21474
Automatic update from web-platform-tests
Drop pypy from tox.ini
This has been broken for a while due to https://bitbucket.org/pypy/pypy/issues/3157
--
wpt-commits: 9469d80dc489346bb2f8e71c35ad1d350b4d649d
wpt-pr: 21522
Automatic update from web-platform-tests
Clamp the presentation time to a usable range
If the time container is seeked to a large enough value, we will end up
truncating it to SMILTime::Latest(), which is the largest value that
isn't one of the two special values ("indefinite" and "unresolved").
When trying to derive other values from this value - like if we have an
interval begin at it - we can end up in a loop since any the result of
any additions will yield the same value, leading to the element being
rescheduled at the same point in time, hanging UpdateIntervals().
This mechanism can also be used to implement the "once" animation-policy
in a slightly nicer way. This will be done as a follow-up.
Bug: 1039886
Change-Id: If13d7d7d3c44c4f586d15852eb05105879f44918
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030885
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#737260}
--
wpt-commits: 0db6154c63f5412dd557b1ae70acd17bc1c32b25
wpt-pr: 21514
Automatic update from web-platform-tests
Support crashtests in testfiles.affected_testfiles (#21531)
Co-Authored-By: Robert Ma <robertma@chromium.org>
--
wpt-commits: c7227ea61e08f972023767b22cbea7ab23209426
wpt-pr: 21531
Automatic update from web-platform-tests
Resize Observer - Simple content-box and border-box observations
It is possible to now observe changes to content box and border box of
an element that is being observed. However, changes to an element's
content box without a change in its border box can not be observed yet,
and will be addressed in a subsequent change.
Bug: 1042537
Change-Id: I6415fc4f5cec783cc717051c11b2fdd95d3a28e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004051
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Commit-Queue: Sahir Vellani <sahir.vellani@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#737369}
--
wpt-commits: 276cbde855f10082da600bef4d2e8432f4e3a9fe
wpt-pr: 21212
Automatic update from web-platform-tests
[webnfc] Support writing/reading local type records
Some notable points:
1) Local type in WebNFC APIs is always prefixed by ':', but, the ':'
will be omitted when it's actually written into the nfc tag.
":act" --> "act" to be written as the TYPE field into the nfc tag.
":text" --> "text"
The reading direction is vice versa.
"act" --> ":act" to be exposed as NDEFRecord#recordType.
"text" --> ":text"
2) Only "smart-poster", external, and local type records are supposed to
be able to carry a ndef message as payload.
3) Local type is only expected to exist inside a ndef message that is
another ndef record's payload. Top level ndef message is not allowed
to have a local type record.
The spec changes:
https://github.com/w3c/web-nfc/pull/491https://github.com/w3c/web-nfc/pull/493https://github.com/w3c/web-nfc/pull/495https://github.com/w3c/web-nfc/pull/502https://github.com/w3c/web-nfc/pull/506
BUG=520391
Change-Id: Ic2890c031109aa583437ac93a8901ff71992af78
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1996946
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Leon Han <leon.han@intel.com>
Cr-Commit-Position: refs/heads/master@{#737290}
--
wpt-commits: a1652e2faab5c92db0d3a2523ef9a94003e1e8f5
wpt-pr: 21157
Automatic update from web-platform-tests
ServiceWorkerSingleScriptUpdateChecker has credentials
Before the new byte-for-byte checking, credentials_mode was set to
kInclude for imported scripts. However,
ServiceWorkerSingleScriptUpdateChecker sets the flag to kOmit because
it's missed from the current spec. This CL is to correct the mode to
fix the unintentional change.
Spec issue: https://github.com/w3c/ServiceWorker/issues/1497
Bug: 1042159
Change-Id: I553d7bec015eb4cb80f7f59c640f26491fa02b75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032689
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737253}
--
wpt-commits: acc51c1f9cb98db4419132c4cf8510c13e958f0f
wpt-pr: 21528
Automatic update from web-platform-tests
[WPT] Remove testharness-helper.sub.js
This CL migrates
wpt/content-security-policy/securitypolicyviolation/upgrade-insecure-requests-reporting.https.html
to use the new /common/security-features/ infrastructure.
This CL removes the last use of
wpt/upgrade-insecure-requests/support/testharness-helper.sub.js
(other tests under wpt/upgrade-insecure-requests/ have been
already migrated) and thus removes the file.
Follow-up of a comment at
https://chromium-review.googlesource.com/c/chromium/src/+/2024249
Bug: 906850
Change-Id: I7a992491652d988115d1d9e62eafe179473e534a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027899
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Eriko Kurimoto <elkurin@chromium.org>
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737307}
--
wpt-commits: 87011862748b009f7ef5134f23315655e1600073
wpt-pr: 21497
Automatic update from web-platform-tests
Set network_isolation_key for signed exchange cert fetch (#21511)
Currently network_isolation_key is not set for signed exchange cert fetch.
So, even if the signed exchange and the certificate were prefetched,
the certificate is fetched again while navigation when
SplitCacheByNetworkIsolationKey is enabled.
Bug=1047110
Change-Id: I524df1da097c6f544777f20cca5a3e53246693cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029564
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737251}
Co-authored-by: Tsuyoshi Horo <horo@google.com>
--
wpt-commits: 171fdd773bef185a7b4adb9238d090141dbee3fa
wpt-pr: 21511
Automatic update from web-platform-tests
Fix#4813: document when screenshots are taken for visual tests
--
wpt-commits: 638f1774d565ba228feee10dc3707dea566bc45f
wpt-pr: 21523
Automatic update from web-platform-tests
Test the CSS round() function. (#21506)
* Test the CSS round() function.
* Indent with spaces.
* Sigh, don't shadow the test() function with an argument name.
* assert_not_equal*s*(); the weird grammar of that name always messes me up
--
wpt-commits: 5c5f1c18f51f5774b67cfd6672b88dae3fa8af25
wpt-pr: 21506
Automatic update from web-platform-tests
Use parseFloat() to parse CSS pixels values in two WPT
Two WPT use CSSNumericValue.parse() to parse CSS pixel values, which
makes the tests basically Chrome-only. This patch changes them to use
parseFloat() directly so that other browsers can pass.
Bug: 441925
Change-Id: I01d6d2999cf4266bd6d3bda521d2bdfc8732ab7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031932
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737036}
--
wpt-commits: f6e67637596cccd6bd38b8837440b394b9e14aef
wpt-pr: 21519
Automatic update from web-platform-tests
Mark wpt/cookies/http-state/{general,name}-tests.html slow
Seeing some flakiness due to timeouts in them, and they do look like they
do a lot of things.
Bug: 1047067
Change-Id: I1892f35a8047fdad8c50aeafc2da54665b522bc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031364
Reviewed-by: Lily Chen <chlily@chromium.org>
Commit-Queue: Maksim Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736938}
--
wpt-commits: 78ca07deef3efc7aea53ae69f17eadcc92af5544
wpt-pr: 21516
Automatic update from web-platform-tests
ConvolverNode channel count and mode can be changed
The channelCount and channelCountMode for a convolver node is no
longer fixed. The count can be 1 or 2 and the mode can be set to any
valid value other than "max". This is basically the same constraints
as for a StereoPannerNode.
Also see https://github.com/WebAudio/web-audio-api/issues/2050
Feature: https://www.chromestatus.com/feature/6248507407073280
Bug: 1021552
Change-Id: I1cd814376d88ff4a525bae1f5e608ca4b989ac07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988714
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736899}
--
wpt-commits: 7b7fb5c3e26d92be655cbca00a233fbe4243c085
wpt-pr: 21493