Automatic update from web-platform-tests
Cookie Store API: Fix crashes on http://localhost.
Issue #1:
The "SecureContext" IDL attribute considers localhost to be secure, but
the Cookie Store API assumed that it would only be exposed on
cryptographically secure origins, so a DCHECK caused attempts to
set/delete cookies on http://localhost to crash.
This CL replaces the DCHECK with an exception that is thrown on attempts
to set/delete secure cookies on cryptographically insecure origins.
Issue #2: The "secure" cookie attribute defaulted to true.
Setting/deleting a secure cookie on a cryptographically insecure origin
is prohibited. The cookieStore.delete() API excluded the option to set
the "secure" attribute, however, so there was no way to delete an
insecure cookie.
This CL defaults the "secure" attribute to true on cryptographically
secure origins, and false otherwise.
Bug: 956641
Change-Id: Iff7c22713e8604d60b68d42199a74b2d08235712
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1700357
Commit-Queue: Staphany Park <staphany@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#681054}
--
wpt-commits: 2e135c03ff73a7102011f4e610dc7890eb4332a1
wpt-pr: 17988
Automatic update from web-platform-tests
[WPT/common/security-features] Add delivery_key
This CL adds `delivery_key` to spec.src.json down to
the JSON objects supplied to JavaScript test runners,
to distinguish referrer-policy and mixed-content tests
explicitly by data fields.
Generated files will be updated after some more changes, not now.
Bug: 906850
Change-Id: Iedae7830cbc41eb87ab884a88aa9e667cc54f6e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717109
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#681032}
--
wpt-commits: 2c422b2075e70226d9f531d684915798a33e8259
wpt-pr: 18068
Automatic update from web-platform-tests
Move internal xr tests to wpt_internal/webxr
This allows the two sets of tests to run the same infrastructure, and
ensures that they will stay more closely in sync. This also allows
for easier porting of the tests and more consistency in the tests.
Bug: 959476
Change-Id: I8eca0372a4091dd27702b099eb3836bfe9d6648d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717328
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#681021}
--
wpt-commits: 7f168d2902db1dd889b314f597f38148ffcdc963
wpt-pr: 18058
Automatic update from web-platform-tests
Include typedefs as idlharness dependencies (#18006)
* Include typedefs as dependencies
* Fix credential-management
* Add FileAPI dep to html/dom interfaces test
--
wpt-commits: bc908ac5428cd665341ff7c990fccfb95d3f07ef
wpt-pr: 18006
Automatic update from web-platform-tests
[idlharness.js] Handle callbacks in very basic manner (#18085)
* Handle callbacks in very basic manner
* Drop todo, keep new Document()
--
wpt-commits: 53f176da20d4a91bc59729472bf1a0ec1399073b
wpt-pr: 18085
Automatic update from web-platform-tests
MathML: Avoid more false negative results for fraction reftests (#18086)
This also introduces improvements to MathMLFeatureDetection:
* Introduce has_mfrac().
* Split mathml source into several lines for better readability.
* Add reference links to core spec.
* Fix detection for lspace/rspace (measure the mrow container instead of mo).
* Add helper function to check a feature for match reftest and otherwise
force failure by displaying a red square at the top left corner.
--
wpt-commits: f1e6032e71849ee5ed11b5794406dd9ebd4bcdf6
wpt-pr: 18086
Automatic update from web-platform-tests
Enable persistent toasts by adding functionality for duration Infinity
This change allows users to show() toasts that will persist indefinitely
by passing through duration: Infinity. The change also adds range boundaries
to duration, so the value must be greater than 0.
Bug: 985468, 972945
Change-Id: I694edab74aff7f99e770e7d37373329f5e663c99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713684
Commit-Queue: Jack Steinberg <jacksteinberg@chromium.org>
Reviewed-by: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680574}
--
wpt-commits: 49dfd42d43a2927760e0fcc8cdb5b2626fafde67
wpt-pr: 17981
Automatic update from web-platform-tests
[Native File System] Remove Writable File Stream code
Removing Writable File Stream code for now until we decide what we want
to do as an API using Writable Streams.
As currently designed, the API does not take into account SafeBrowsing
and Quarantine checks.
Bug: 986865
Change-Id: Ib5bb922359cae1fb8267cd7123345bab6de78090
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717590
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Auto-Submit: Olivier Yiptong <oyiptong@chromium.org>
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680866}
--
wpt-commits: f88d17122816b73fe02ea3da19021f08b67a6743
wpt-pr: 18062
Automatic update from web-platform-tests
[LCP] non-trusted event does not stop the metric (#18083)
* [LCP] non-trusted event does not stop the metric
* Changed test description
--
wpt-commits: f1e49a47d5c06e66f184dbbb028567f2a35f3e9b
wpt-pr: 18083
Automatic update from web-platform-tests
[Trusted Types] Add "sample" value to SecurityPolicyViolation reports.
The reporting format is specified, but still subject to change.
The details are found in the "Integration with Content Security Policy"
chapter of the current Trusted Type spec.
https://wicg.github.io/trusted-types/dist/spec/#integration-with-content-security-policy
Bug: 739170
Change-Id: I4b85af4a6faf2387a24479a121b2c243ab83f350
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715688
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680847}
--
wpt-commits: ce6fd690a4ac1be7adeeb546a53dd134df931301
wpt-pr: 18047
Automatic update from web-platform-tests
ElementTiming and LCP: add fully active check
The element attribute getter should only return the element when the
document is fully active. This check is done similar to other places
such as Fullscreen::RequestFullscreen. Tests are added.
Bug: 879270, 942033, 942033
Change-Id: Ie90c25ab5d07d03ccb1f9fe330d074c407aeeb7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717238
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680841}
--
wpt-commits: 56edb11ce6572c819c13b4e01340fa91ed426ef1
wpt-pr: 18057
Automatic update from web-platform-tests
Handle display:contents for viewport propagation.
When documentElement/body does not generate a box, its background will
not propagate to the viewport (see [1]). This removes the need
for calling EnsureComputedStyle() on documentElement/body.
The CSSWG has also resolved that to be the case also for other
properties propagated to the viewport[2].
Some of the wpt tests for body propagation didn't actually have a body
element. Added.
[1] https://drafts.csswg.org/css-backgrounds/#special-backgrounds
[2] https://github.com/w3c/csswg-drafts/issues/3779#issuecomment-481762912
Bug: 987207
Change-Id: I06e618e2acd2926b5ae4831bf5825e13e970d035
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547974
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680834}
--
wpt-commits: d40f18ae072cab633cfb34fb883e12c87c1bc191
wpt-pr: 18039
Automatic update from web-platform-tests
MathML: Add tests for embellished operators (#18081)
See https://mathml-refresh.github.io/mathml-core/#embellished-operators
These tests assume that operator spacing is supported, so a feature detection
is added to prevent false negative results. This new detection is also used
for space-like tests which rely on the same assumption.
Minor tweak for mspace detection: compare `<mspace width="20px">` against
`<mspace>`, just in case the latter is nonzero in some browsers or tests.
--
wpt-commits: 7e9bfd839d6b19555d947447ae996f11ac86facc
wpt-pr: 18081
Automatic update from web-platform-tests
MathML: Prevent false negative results when mspace is not supported. (#18059)
Many testharness tests rely on the <mspace> to draw boxes inside math formulas
and test MathML layout. When this element is not supported (e.g. lack of
MathML support) the boxes are basically empty and this leads to many false
negative results, especially because tests also allow some rounding errors.
More generally, for several tests it is assumed that some more basic
features are supported in order to perform their verifications.
This commit introduces a new MathMLFeatureDetection helper class to perform
such verifications and avoid false negatives results. One detection is added
for the <mspace> element and several presentation-markup tests relying on this
element are updated to perform this feature detection prior to runnig the
actual checks. This could be improved in the future, this is just fixing the
most serious issues.
--
wpt-commits: 6550e91cd39dde7597b780f2d643a1a131837012
wpt-pr: 18059
Automatic update from web-platform-tests
Fix document.all test to pass even when run directly in a browser.
The test has a <div id="log"> that comes _after_ the <script> that runs the
tests. That means that when logging is enabled (e.g. loading the test
directly) testharness doesn't find the log container, since it hasn't been
parsed yet when the test runs. It then creates a new <div id="log"> and
inserts it into the DOM, which changes the contents of document.all and the
test fails. On the other hand, when running in a harness logging is typically
turned off so none of this happens.
The solution is to move the log container to before the test script and modify
the test expectations accordingly. Then the test passes in both modes.
--
wpt-commits: ed3eaa5a9b5f104ffdd2c76ae51888df2e17e66c
wpt-pr: 18060
Automatic update from web-platform-tests
Add idlharness test for element-timing (#18064)
--
wpt-commits: b6c413217de9e91590fbac9868a5720e918d4d2e
wpt-pr: 18064
Automatic update from web-platform-tests
[IntersectionObserver] Fix for rtl clipped explicit root
IntersectionGeometry::ClipToRoot uses MapToVisualRectInAncestorSpace
to map the intersection rect up to the coordinate system of the
root element's overflow rect. It then explicitly translates the
intersection rect to the root element's coordinate space and applies
the root element's clip (if any). This patch fixes the coordinate
space mapping for the case of a root element with overflow clip and a
non-zero scroll origin (e.g., direction:rtl or
flex-direction:row-reverse).
BUG=939614
R=chrishtr@chromium.org
Change-Id: I15dce9456e9791510bb331bf0cfbabd4cb04f9c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717688
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680761}
--
wpt-commits: 8aa5717cff0397f356dd494a4257fd94e60035b3
wpt-pr: 18065
Automatic update from web-platform-tests
Revert "Re-write test pointerevent_pointermove_in_pointerlock.html"
This reverts commit 9b7bafff73e59dc5d0cfcd0f499aa20be66bca54.
Reason for revert: Causing leak failures on WebKit Linux Leak bot
https://luci-milo.appspot.com/p/chromium/builders/ci/WebKit%20Linux%20Leak/2348
Original change's description:
> Re-write test pointerevent_pointermove_in_pointerlock.html
>
> The test was failing in wpt because it passing non-integer value to
> test driver. This CL changes it to use "origin" instead.
> This CL rewrites the test to makes it cleaner, instead of adding event
> listener inside event listener.
> This CL also changes the test to send the "move" events after receiving
> pointerlockchange.
>
> Bug: 986277
> Change-Id: I0f51523c3c90791339877b2e51afa8e9a4cc9d4d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717195
> Reviewed-by: Lan Wei <lanwei@chromium.org>
> Commit-Queue: Ella Ge <eirage@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#680563}
TBR=lanwei@chromium.org,eirage@chromium.org
Change-Id: Ia53d1066363ceaf804f61ada369a4126c859f875
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 986277
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716038
Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680743}
--
wpt-commits: a285d1bbbc1921bc976aab1af4238a8e304ecbab
wpt-pr: 18066
Automatic update from web-platform-tests
Organize webxr internal and external tests
Moves all remaining internal webxr tests that can be made external to
external/wpt/webxr. For tests that were not moved a comment was added
explaining what is keeping the test internal. And a README was added to
also call out these requirements.
Most tests were ported as-is (with the exception of changing the scripts
that they include), but substantial updates were required to a couple
in order to better align with the spec:
xrWebGLLayer_constructor was modified to be more similar to the deleted
xrWebGLLayer_incompatible_device, since that also tested the constructor
just with a gl context that had not yet been made xrCompatible. This
test is now more explicit about what it is doing.
render_state_vertical_fov_inline was cloned to an external version that
tests that setting a value below the min or above the max stays inside
the min and max range, but does not test the specific expected value,
since that is not required by the spec. Chrome is keeping an internal
version of that test with it's chosen min/max.
Bug: 863557
Change-Id: I81d6d4bbbdf7e60e8576eb6a8dfbd422aa95013e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715732
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680665}
--
wpt-commits: 453453af2e854b13228cab2da314cc2a4d1ffc86
wpt-pr: 18026
Automatic update from web-platform-tests
Indexed DB: Migrate "Structured Clone" test to WPT
Pros:
* Switch from js-test to testharness
* Cover a bunch more ECMAScript and Platform types
* Runs in Window and Worker contexts
* Decreases coverage for FileList interface
* Somewhat redundant with WPT's html/infrastructure/safe-passing-of-structured-data
Cons:
Change-Id: If80ce64a88caa9b3d0e409bdac5712ca795a1785
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1709787
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680653}
--
wpt-commits: d0691cc870b3ea1f5dc516f53817d2c3377aab9a
wpt-pr: 17951
Automatic update from web-platform-tests
[css-properties-values-api] Reify specified values as CSSUnparsedValue
According to a recent spec change, the syntax of a registered custom
property must be ignored until computed-value time. This means that
we can unfortunately not reify specified values according to the
syntax; instead all custom properties reify as CSSUnparsedValue,
regardless of their registration status.
This means that we can remove large parts of the Typed OM code which
deals with PropertyRegistation for specified values and matching of
incoming CSSStyleValues against registered syntax.
The typedom.html test was also mostly re-written, as most of the things
it tested are now not relevant anymore, or at least no longer as
interesting as before. (The new reworked test basically verifies that
registered custom properties behave as unregistered for
attributeStyleMap and styleMap. For computedStyleMap, we should of
course still reify according to the syntax).
Bug: 641877
Change-Id: I4da7c25b8f066dd01388b6229bebe181513e9fd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713557
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680595}
--
wpt-commits: 8c0c1caee779ea4ad0dee2484be0234d14f54b7b
wpt-pr: 18032
