Automatic update from web-platform-testsMerge pull request #12847 from mrego/css-contain-stacking-context
[css-contain] Containment and stacking contexts for inline elements
--
wpt-commits: 7d0d45d65796520f94eda3d4de3986b84e7173ab
wpt-pr: 12847
Automatic update from web-platform-testsMerge pull request #12823 from web-platform-tests/revert-12492-contain-support
Revert "[css-contain] Add support file in local directory"
--
wpt-commits: e54519b77a611d45d8f495a3344eca6a840d6fd3
wpt-pr: 12823
Automatic update from web-platform-testsPaymentRequest: Implement PaymentResponse.payerdetailchange event (#12846)
The event handler is triggered when the user changes payer information
such as payer name, payer email, or payer phone in the user interface.
Related spec change:
https://github.com/w3c/payment-request/pull/724
Test:
payment-request/payment-response/onpayerdetailchange-attribute.https.html
payment-request/payment-response/onpayerdetailchange-attribute.manual.https.html
Bug: 861704
Change-Id: Ia5d63f53874abd7c76014bf35379a71a0eead622
--
wpt-commits: 3c6c9350988f98c8fac94fab8174bc4729cd6755
wpt-pr: 12846
Automatic update from web-platform-tests[cookies] Correct utility function and tests (#12835)
* [cookies] Fail on exceptional circumstance
Some tests which use the `credFetch` utility include assertions only for
the absence of cookies. Because `fetch` does not reject the returned
promise for valid HTTP responses outside of the 2XX range, these tests
could be satisfied by querying non-existent URLs. This is not an issue
in any existing tests, but it has the potential to hide problems in
future patches.
Update the `credFetch` function to report unsuccessful requests as
failures.
* [cookies] Correct utility function and tests
The `cookie-helper.sub.js` utility script includes
`set_prefixed_cookie_via_http_test`, a function that defines sub-tests
using the `promise_test` API. Previously, it included the following
code:
promise_test(t => {
var postDelete = _ => {
// (elided)
};
if (!options.origin) {
return postDelete;
} else {
// (elided)
}
});
The `promise_test` function does not recognize return values which are
functions, so returning the `postDelete` method had no effect, and as a
result, the generated tests performed zero assertions. Because none of
the consumers of `set_prefixed_cookie_via_http_test` specified a value
for the `origin` option, all invocations were effected by this bug.
Correcting the problem surfaced a number of errors in the tests. In the
interest of atomicity, this patch attempts to address them all:
- The logic intended to defensively remove cookies prior to testing was
implemented using `document.cookie`. Because some tests create cookies
which include the `HttpOnly` attribute, the DOM API cannot remove
cookies in all cases. This patch refactors the solution to remove
such cookies via an HTTP request. It also assumes the environment is
initially clean and instead expresses the concern via an asynchronous
"cleanup" function. (This change necessitated an extension to the
`set.py` script so that it could be used to expire cookies.)
- The test name `__secure.header.html` incorrectly asserted that a
cookie set with the `Secure` attribute could be observed in a
non-secure context. This patch corrects the expectation.
- The test named `__secure.header.https.html` incorrectly asserted that
a cookie set with a foreign `Origin` attribute could be observed from
the current origin. This patch corrects the expectation.
--
wpt-commits: 88d4f4cc118320c4e02003ffc1ba2c5ee81b1753
wpt-pr: 12835
Automatic update from web-platform-tests[LayoutNG] Add LayoutBox::PercentageResolutionLogicalHeight.
This function allows LayoutNG to correctly query the percentage
resolution block_size in quirks mode. (see test case for an example of
where this happened).
We call this as we are crossing a legacy->LayoutNG boundary while
creating the constraint space from a LayoutObject.
The function will also be used in the CSS Layout API to provide the
correct percentage resolution size.
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I295145996f2460de1b25f85ff3784df6d6edbd30
Reviewed-on: https://chromium-review.googlesource.com/1194072
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589074}
--
wpt-commits: a806d658df3bcc3f05675ad8d08a6e109177c6b0
wpt-pr: 12855
Automatic update from web-platform-testsFix cases where setValueCurveAtTime was not throwing errors
Catch more cases where we should throw errors if a new
setValueCurveAtTime overlaps an existing setValueCurveAtTime event.
Add some additional tests for more coverage. Also, some of the
existing tests were using incorrect expected error types so fix them.
Remove test expectations file since we pass now.
Bug: 879767
Test: the-audioparam-interface/audioparam-setValueCurve-exceptions.html
Change-Id: I14a7a7c9ab36955b7e084ca9148495860b661111
Reviewed-on: https://chromium-review.googlesource.com/1205719
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589059}
--
wpt-commits: 9f63e45e03bb836556466ba43082c4a1c464b14e
wpt-pr: 12837
Automatic update from web-platform-testsThrow errors for invalid rolloffFactor and coneOuterGain
The WebAudio spec says we must throw errors for a negative
rolloffFactor and for a coneOuterGain outside the interval [0,
1]. Make it so.
Also add some additional tests to ctor-panner.html to verify that a
rolloffFactor of 0 or 100 do not throw errors and that a
coneOuterGain of 0 or 1 do not throw errors.
Remove invalid tests from panner-rolloff-clamping.html because
negative rolloffFactor now throws an error.
Finally remove text expectation for ctor-panner.html test, which
passes now.
Bug: 879845
Test: the-pannernode-interface/ctor-panner.html, the-pannernode-interface/panner-rolloff-clamping.html
Change-Id: Ie90e9fe13e82fd3cc955060dc9e77266ef4ff591
Reviewed-on: https://chromium-review.googlesource.com/1205099
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589045}
--
wpt-commits: 7b9c733915fab4723a453e03d692f9c396a8c6fb
wpt-pr: 12834
Automatic update from web-platform-tests[wptrunner] Reject tests that almost time out
In stability check (wpt run --verify), reject tests that almost time
out, i.e. take more than 80% of the timeout allowed to run). These tests
will be listed in a new section, "slow tests", in the output.
Fixes#9972.
--
Take timeout_multiplier into account
--
Longest duration for each status of each test
Previously we record the longest duration of all tests. However, each
test can have different timeout. Besides, test runs with different
results should be considered differently; runs that time out should be
ignored.
Therefore, we now keep track of the longest duration for each result
status of each test.
Also add a unit test.
--
Fix ci/check_stability.py
--
wpt-commits: 20f4a6dcec93d3ea65a8dd5c3b3a3dbe30476ae6, 0ccdf9b766875ae82000aa88c6c011c6cbd08430, 5a540d04ef8d14f77e0afa9f139788a45c7a65d3, 69717e2cdc71420593c3eedf6d370cb397b5b621
wpt-pr: 11570
Automatic update from web-platform-testsElement::setAttribute() modified to accept TrustedTypes
Element::setAttribute() modified to accept generic TrustedType
(StringOrTrustedHTMLOrTrustedScriptOrTrustedScriptURLOrTrustedURL)
(the name will be changed later).
This is the implementation used for setting attributes explicitly.
Added virtual GetCheckedAttributesNames() method, overriden in
HTMLXXXElement files, to return list of names of attributes that
need to have values checked against Trusted Types.
Added new implementations of Element::setAttribute(),
one per each Trusted Type, to be used internally
in HTMLElement functions.
Corrected existing TrustedXXX::GetString() implementations
to be concise.
Added TrustedScriptURL::GetString().
Bug: 739170
Change-Id: I3a9f51cbed5d75f8059141738b419cc66e529006
Reviewed-on: https://chromium-review.googlesource.com/1146563
Commit-Queue: Maja Kabus <kabusm@google.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588867}
--
wpt-commits: ef04d8b0f2e9a65ef82b33e03978ec0b34ec8c29
wpt-pr: 12764
Automatic update from web-platform-testsReturn a 404 when trying to access a .any.* path that doesn't exist. (#12849)
--
wpt-commits: cb4c37d196f1bf49f3c04b1ac077c392714b65ea
wpt-pr: 12849
Automatic update from web-platform-tests[css-properties-values-api] Reify values from styleMap.get.
This CL gives return values from element.styleMap.get the correct type
according to the current PropertyRegistration.
The expected behavior is exactly the same as for attributeStyleMap, so
those tests have been adapted to run for both API entry points.
Note: PrepopulatedComputedStylePropertyMap is available in worklets,
where the ExecutionContext is not a Document, but we don't need to
reify values in this case, because already-reified values are "pushed"
rather than "pulled". (See ::UpdateStyle).
Note: Exit ParseIfRegistered before registration lookup. This avoids
the lookup if we already know that we won't need it (which is the case
for [Prepopulated]ComputedStylePropertyMap).
Bug: 641877
Change-Id: Id54a22079c88368efccc372d01252fa3e7734d10
Reviewed-on: https://chromium-review.googlesource.com/1201302
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588840}
--
wpt-commits: ba2287be3eb16c7c8b6f0ced3680a539309b2a14
wpt-pr: 12827
Automatic update from web-platform-tests[css-contain] Fix size containment in elements with scrollbars
To determine the size of an element with "contain: size"
we should treat it as having no contents
(https://drafts.csswg.org/css-contain/#containment-size).
Scrollbars are not part of the box's contents,
so we should take them into account to determine box size.
BUG=872794
TEST=external/wpt/css/css-contain/contain-size-scrollbars-001.html
Change-Id: I166af8469243a9c3b52c3e30569d1d81c3de6e9e
Reviewed-on: https://chromium-review.googlesource.com/1206210
Commit-Queue: Manuel Rego <rego@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588809}
--
wpt-commits: b778f69ee0d2a1080191d58f9d6eeb9c950b19d4
wpt-pr: 12840
Automatic update from web-platform-testsFetch: align CORS test with new "safelisted headers" rules
See https://github.com/whatwg/fetch/pull/736 for context.
--
wpt-commits: efa5cebbd4a2b5df055a12212c534b13052154b8
wpt-pr: 12797
Automatic update from web-platform-testsDevice Sensor: Remove placeholder enumerator values in the sensor::SensorType
According to the mojo style guide:
https://chromium.googlesource.com/chromium/src/+/master/docs/security/mojo.md#do-not-define-placeholder-enumerator-values
It is recommended not to define placeholder enumerator values. Currently,
sensor::SensorType defines two such values: FIRST and LAST. This CL removes
these two placeholder values.
Bug: 870781
Cq-Include-Trybots: luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I8b275bc5680c8c0d97fe2e7208301d6f33236cbe
Reviewed-on: https://chromium-review.googlesource.com/1197423
Commit-Queue: Jun Cai <juncai@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588678}
--
wpt-commits: bdf21e69ffaeb96097dfbc0888e4d9eb5413fed2
wpt-pr: 12769
Automatic update from web-platform-testsdocument.open(): Test non-fully active documents (#12770)
For https://github.com/whatwg/html/pull/3977.
--
wpt-commits: 61bc4ecc726596e5ce8634752e09a5e8a20e060f
wpt-pr: 12770
Automatic update from web-platform-tests[Background Fetch] Record via UMA whether a fetch has duplicate requests
Also reject the registration if that happens with a warning, and add a
failing WPT test.
Bug: 871174, 780025
Change-Id: Ibdcc49bc47ea959e0c255a48f5d090cb865a6e45
Reviewed-on: https://chromium-review.googlesource.com/1202262
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588614}
--
wpt-commits: 98c37ef258eb21fb1c3dbf508437e58be21c2145
wpt-pr: 12830
Automatic update from web-platform-testsbindings: Set function name for attribute accessors
This aligns the behavior with the current Web IDL specification as well as
Firefox and Safari.
Bug: 878074
Change-Id: Ia862c1d0d8319fb78726817b69f9151e5fb500fd
Reviewed-on: https://chromium-review.googlesource.com/1191727
Commit-Queue: Timothy Gu <timothygu@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588544}
--
wpt-commits: 31f62ee2b6103a94aafa6ffd5e205c8898f4b9ba
wpt-pr: 12765
Automatic update from web-platform-testsRemove kereliuk from suggested reviewers (#12829)
I'm no longer working on WPT to focus on a new project.
--
wpt-commits: a0f75fcad81bee1dbe35d30c94aed9b7630d9dda
wpt-pr: 12829
Automatic update from web-platform-testsString_list_directive created
Created a primitive version of function AllowTrustedTypePolicy
"require-trusted-types" changed into "trusted-types" and takes a list of policy names
createPolicy updated to throw when policy name is not allowed
Tests added for policy creation attempt when policy name is on the whitelist and when it isn't
Tests added fot policy creation attempt with no whitelist given
Poked at existing tests to change "require-trusted-types" into "trusted-types"
Removed boolean require_safe_types_ from csp_directive_list
Bug: 739170
Change-Id: Ida0188cf38f8edba8b966b2f708b7a7919d08b29
Reviewed-on: https://chromium-review.googlesource.com/1186325
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Orsolya Bernadett Batiz <orsibatiz@google.com>
Cr-Commit-Position: refs/heads/master@{#588496}
--
wpt-commits: 1de1550e95396f979da97620a289c213acaf55e2
wpt-pr: 12798
Automatic update from web-platform-testsWPT: More refactoring navigation-redirect.https.html
This makes the test more extensible. Preparation for adding tests for
the Clients API and resultingClientId. Specifically, the requestInfos
from the workers and the expectations will have a resultingClientId
in addition to the URL.
Bug: 876223, 778497
Change-Id: Id7c25a77f43f33d40b64ea77c2cf51a0745f57c6
Reviewed-on: https://chromium-review.googlesource.com/1203711
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588479}
--
wpt-commits: d4fb17e0338a3b412af81244d7254cd2b9bc27a0
wpt-pr: 12820
