Automatic update from web-platform-testsCorrect serialization of URL in background-332.html (#10478)
* Correct serialization of URL in background-332.html
According to https://drafts.csswg.org/cssom/#serialize-a-url, the serialization of a URL always includes double-quotes, and per https://drafts.csswg.org/css-values/#relative-urls, if a URL appears in a computed style, it is resolved to an absolute URL. Adjust background-332.html to match the spec, and update the test description to clarify the computed style is being tested.
--
wpt-commits: b792706b1001a1e8d93b26e8cea341ecffe8417e
wpt-pr: 10478
Automatic update from web-platform-testsWorker: Change the default credentials option from 'omit' to 'same-origin'
This is a follow-up for the spec change:
https://github.com/whatwg/html/pull/3656
Note that ES Modules for dedicated workers is still behind the flag and this
change doesn't affect applications in the real world.
Bug: 848247
Change-Id: I25083f3f11f9d13663e16e2f4c137095e9b12b01
Reviewed-on: https://chromium-review.googlesource.com/1080668
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563465}
--
wpt-commits: 72c7cfed684554c0d65b7a33d413df9ae1c5999f
wpt-pr: 11274
Automatic update from web-platform-tests[css-grid] Baseline alignment inside the tracks sizing algorithm
We have identified several cases where the Baseline Alignment accounts
for the grid's intrinsic size. Since we depend on the track sizing
algorithm to compute the grid's intrinsic size, the only way to handle
all these cases is to integrate the baseline alignment logic in the
algorithm.
Additionally, the CSSWG has identified several cases that can't be
solved properly; such cases have in common that they imply cyclic
dependencies between the item's and grid area's size. The CSSWG has
resolved that these items don't participate in baseline alignment:
https://github.com/w3c/csswg-drafts/issues/1365
There are also other related issues with some examples and relevant
discussions about this topic:
https://github.com/w3c/csswg-drafts/issues/1039https://github.com/w3c/csswg-drafts/issues/1409
Bug: 704713
Change-Id: I817b16eb43aa76f4827deb8f1f20efb7fde3dc22
Reviewed-on: https://chromium-review.googlesource.com/923261
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Sergio Villar <svillar@igalia.com>
Cr-Commit-Position: refs/heads/master@{#562406}
--
wpt-commits: 82b278966038f26cb83ceeb67404b0ce7e13a74c
wpt-pr: 9553
Automatic update from web-platform-testsRemove tests for the crop property (#10556)
There is a comment in the test that it wasn't implemented in anywhere, and it seems to have been removed from the spec (per 7f3fb42152). Remove the reference to the property from the testcases.
--
wpt-commits: f6867415601bc07b2801900b5d1cae9359612d07
wpt-pr: 10556
Automatic update from web-platform-tests[PageLifecycle] Add WPT test for lifecycle's onfreeze callback
Since the onfreeze callback is invoked based on an internal decision
from the browser, to be able to test the callback, we are adding support
for it from chromeGPUBenchmak as well as in chromedriver/WebDriver.
This CL focuses on the chromeGPUBenchmark solution.
The WPT test itself, verifies that the onfreeze callback is called, and
it also verifies that only fetch keepalive is allowed from withing the
callback.
Bug: chromium:837709
Change-Id: Ia4cb16dc10625f478ec270617da1a26395a9d29d
Reviewed-on: https://chromium-review.googlesource.com/1072899
Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Reviewed-by: Shubhie Panicker <panicker@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Fadi Meawad <fmeawad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563338}
--
wpt-commits: 3d6920b84bac82c45a8da5c8b04b6da0c64f02fd
wpt-pr: 11165
Automatic update from web-platform-testsMerge pull request #11281 from csnardi/cookie-store-idl
Allow cookie-store IDL test to run even if objects not defined
--
wpt-commits: f172b83c6b6bea611e99d0a79bde72ddbdd60e62
wpt-pr: 11281
Automatic update from web-platform-tests[css-layout-api] Allow passing of serialized data between parent<->child.
This allow arbitary parent<->child communation during layout. A parent
can send data to a child via:
// parent
const fragment = yield child.layoutNextFragment({data});
// child
*layout(children, edges, constraints, style) {
const data = constraints.data; // receive data.
}
And child to parent via:
// child
*layout() {
return {data};
}
// parent
const fragment = yield child.layoutNextFragment();
const data = fragment.data; // receive data.
As the parent and child layouts may be invoked in different worklet
global scopes, and don't allow data shared, the serialization of data
uses "kForStorage" which means that SharedArrayBuffers aren't allowed
in the serialization.
Serialization also occurs so that we are able to cache results.
Bug: 726125
Change-Id: Ib7e81b5778cef3af2c2f8a1ccef749f1d2ba4dfa
Reviewed-on: https://chromium-review.googlesource.com/1072150
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563235}
--
wpt-commits: 8c8238ca96f913c1b90f838def7f9cf0253c0113
wpt-pr: 11166
Automatic update from web-platform-testsMove HTML from untested IDL to a dependency IDL for DOM
The DOM idlharness test would not run as dependencies for the HTML IDL file were not declared. However, we don't need to define HTML as untested IDL -- using the new dependency IDL feature generates the same tests but prevents the current dependency problem.
--
wpt-commits: 2ae39a003cba3b1292d5239f6043281d9277d25b
wpt-pr: 11252
Automatic update from web-platform-testsHTML: Test hidden attribute on table elements (#11264)
--
wpt-commits: 89dc77674112c00ac5b513b7cdce68a341019f85
wpt-pr: 11264
Automatic update from web-platform-testsRefactor and split up with `variant` all encoding tests
Fixes#11015.
--
wpt-commits: d6c29bef8d4bcdfe4f689defca73360b07647d71
wpt-pr: 11016
Automatic update from web-platform-testsUpdate testdriver.md (#11261)
Fix link to list of special keys.
--
wpt-commits: 219ed4510789fff5d1efddced703bd0289348636
wpt-pr: 11261
Automatic update from web-platform-testsChange Resource Timing default buffer size to 250.
Following a proposed spec change[1], this CL changes the number of entries
buffered by default before the Resource Timing buffer is full.
[1] https://github.com/w3c/resource-timing/pull/155
Bug: 847689
Change-Id: Id93bfea902b0cf049abdac12a98cc4fba7ff1dd3
Reviewed-on: https://chromium-review.googlesource.com/1078107
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Yoav Weiss <yoav@yoav.ws>
Cr-Commit-Position: refs/heads/master@{#563133}
--
wpt-commits: f696c249c6d41c32bdc04d0bec688ee00228a0cf
wpt-pr: 11257
Automatic update from web-platform-testsMigrate fullscreen to use top layer.
Previous attempts of adding and removing to the top layer were done
synchronously. The spec has been updated to do this asynchronously and
this change matches those changes.
Bug: 240576
Change-Id: Ic57a651596c685daa4b32d78421de5db912c106e
Reviewed-on: https://chromium-review.googlesource.com/1066600
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563065}
--
wpt-commits: 1829a42c93e435937db68c8a842fa9b56dd39dc2
wpt-pr: 11206
Automatic update from web-platform-tests[css-contain] Disable paint containment on internal table elements
Text from the spec
(https://drafts.csswg.org/css-contain/#containment-paint):
"... if the element is an internal table element other than
'display: table-cell', ... paint containment has no effect."
The patch disables "contain: paint" for internal table elements
except table cells.
BUG=843329
TEST=external/wpt/css/css-contain/contain-paint-014.html
TEST=external/wpt/css/css-contain/contain-paint-015.html
TEST=external/wpt/css/css-contain/contain-paint-016.html
TEST=external/wpt/css/css-contain/contain-paint-017.html
TEST=external/wpt/css/css-contain/contain-paint-018.html
TEST=external/wpt/css/css-contain/contain-paint-019.html
Change-Id: I975950ab72fe5cc5aa106fa5fdafd37c64dd6d85
Reviewed-on: https://chromium-review.googlesource.com/1078868
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#563000}
--
wpt-commits: 76860d7aee0c9e0992f812123f47e8cc07f9e201
wpt-pr: 11246
Automatic update from web-platform-testsSupport promises for fullscreen API.
Add ability to store the promises in the pending requests and exits.
Adjust tests to ensure they work correctly with promises.
BUG=383813
Change-Id: I81e4780d5ea25b3a1ac7fef54b1fbc9c0d31897a
Reviewed-on: https://chromium-review.googlesource.com/1075711
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562946}
--
wpt-commits: 0fae4aa0c51c6193ef1b2b74a61352b832d95cfa
wpt-pr: 11207
Automatic update from web-platform-testsMerge pull request #11072 from gsnedders/merge-w3ctestlib
Merge w3ctestlib and apiclient into web-platform-tests as subtrees
--
wpt-commits: 1c7d7b815b29f08856205ab6e426c0e496ca0ef0
wpt-pr: 11072
Automatic update from web-platform-testsEnable the port message queue in /workers/opaque-origin.html
Fixes#11188.
--
wpt-commits: fa9e972c32b8f5e2df1575627dff832744fd17ef
wpt-pr: 11189
Automatic update from web-platform-testsCorrect name of spec in Media Capabilities IDL test (#11258)
My commit adding this test had the incorrect name due to a copy & paste error, this change corrects the name of the spec.
--
wpt-commits: 5914510822645169fccb0a72d997c8f5bca66bbf
wpt-pr: 11258
Automatic update from web-platform-testsidlharness.js: add_dependency_idls: Include partials in attribute type imports.
Change-Id: I57ad6795e9d53b800c70815ba0ab6808849db611
Reviewed-on: https://chromium-review.googlesource.com/1069663
Commit-Queue: Luke Bj <lukebjerring@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562880}
--
wpt-commits: a9980e002815e14ad900fe4864d16296bdbadea7
wpt-pr: 11128
Automatic update from web-platform-tests[LayoutNG] Minor outline bug fix
I found this one by accident in a testharness test. Adding a ref test
that will detect failure. Reftest also passes in FF.
Bug: 835484
Change-Id: I13b58bc8641f24a3fe18d70a1e3850e8e4a30513
Reviewed-on: https://chromium-review.googlesource.com/1077373
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562879}
--
wpt-commits: 22cae554ae0878e7c297efc488a2bcb4ad6cebb8
wpt-pr: 11234
Automatic update from web-platform-testsMove mediasession IDL to interfaces
The mediasession IDL was defined directly in the idlharness test. This change moves the IDL definitions into its own file in interfaces. This change also makes the construction of MediaMetadata be quoted, so the test can proceed even if it is not defined.
--
wpt-commits: 3299400fe83fc70d0058774d22671e86d366e253
wpt-pr: 11253
Automatic update from web-platform-testsMove media-capabilities IDL to interfaces
The media-capabilities IDL was defined directly in the idlharness test. This change moves the IDL definitions into its own file in interfaces. This change also updates the definitions per the latest version of the spec.
--
wpt-commits: 6e632ba33a74d71e3ccff8126e55710f3e5f1b3a
wpt-pr: 11255
Automatic update from web-platform-testsIgnore preventDefault() for 'vertical-scroll'
This CL adds the logic to ensure calling event.preventDefault() will
not block vertical scrolling for frames which do not have the feature
policy enabled.
Essentially, the response from dispatching the dom event is overwritten
by "not canceled" and the event is marked as not prevented. In line with
this, and in order to make sure only vertical scroll is enforced, the
allowed touch action is set to 'pan-y'; then any scrolling along the
x-axis can still be blocked by prventDefault()-ing the event.
Bug: 611982
Change-Id: Iba371be063bf064601ecce6e930424c4fb11ac26
Reviewed-on: https://chromium-review.googlesource.com/1053175
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562856}
--
wpt-commits: c2934c9ddd3c9c8e45b987dd75286e2793192306
wpt-pr: 10942
Automatic update from web-platform-tests[Resource-Timing] Fix `initiatorType` values
There were multiple issues with current `initiatorType` implementation:
* `fetch()` resources had an empty value instead of "fetch"
* `<video>` resources had an empty value instead of "video"
* `<audio>` resources had an empty value instead of "audio"
* `<track>` resources had "texttrack" value instead of "track"
* EventSource resources had an empty value instead of "other"
On top of that, the test to make sure the above is all in check had
some values that were not aligned to the spec, and was disabled due to
the flakiness of audio and video loads.
This CL fixes the above values, fixes the test to be more spec
compliant and enables it.
Bug: 649571, 822757
Change-Id: I1dc6fd35e5e4bc570cbbb7d743dc02279bf42b8b
Reviewed-on: https://chromium-review.googlesource.com/1040925
Commit-Queue: Yoav Weiss <yoav@yoav.ws>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562221}
--
wpt-commits: 0d81b471c71053f3b871a47414233c8f06732e78
wpt-pr: 10840
Automatic update from web-platform-tests[Squad] Use UA styling for form inside table elements.
We did not implement UA style as specified for form elements inside
table elements. This CL removes the hardcoded way of not creating layout
objects and instead add display:none to the UA style sheet as specified.
We introduce a new internal pseudo class :-internal-is-html because the
rule should only apply in html documents. This is also what Gecko does
with its :-moz-is-html. The pseudo class is only allowed in UA sheets.
The relationship with Squad is that we get rid of the dependency on
ancestor layout objects in LayoutObjectIsNeeded.
Bug: 847763, 843520
Change-Id: Ibc83b78493843b1a0503fbb65e509090fe295313
Reviewed-on: https://chromium-review.googlesource.com/1078348
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562789}
--
wpt-commits: 2008aa1e26231e627f94c167c2d4498975276198
wpt-pr: 11244
Automatic update from web-platform-tests[css-grid] Disable paint containment for ruby-text elements
Text from the spec
(https://drafts.csswg.org/css-contain/#containment-paint):
"... if the element is an internal ruby element ...
paint containment has no effect."
The patch disables "contain: paint" for ruby-text elements.
We need to modify the reference file for contain-paint-008 test
because of an unrelated issue (see crbug.com/847743).
Other internal ruby elements like ruby-base, ruby-base-container,
and ruby-base-text-container are already inline elements
so they don't need extra checks.
The tests checking those contain-paint-005, contain-paint-006,
and contain-paint-007 do not pass due to a different issue
related to absolute positions and ruby (see crbug.com/847274).
TestExpectations is updated to point to the actual problem.
BUG=843329
TEST=external/wpt/css/css-contain/contain-paint-008.html
Change-Id: I26814598a3b806b67264146386052cbdfff62847
Reviewed-on: https://chromium-review.googlesource.com/1077387
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#562776}
--
wpt-commits: 2812a9c56bf4d38d2ccc09e31765fe8e62d4d743
wpt-pr: 11240
