Automatic update from web-platform-tests
[js] Remove invalid tests for JavaScript built-ins
The 2015 edition of ECMAScript modified the semantics of a number of
built-in methods to tolerate non-object values [1]. The tests asserting
a TypeError under these conditions are no longer valid.
[1] https://tc39.github.io/ecma262/#sec-additions-and-changes-that-introduce-incompatibilities-with-prior-editions
--
wpt-commits: 32450b4dd65f4a69ba91df20581215a0d81c1daf
wpt-pr: 15333
Automatic update from web-platform-tests
Revert "Don't use HEAD or FETCH_HEAD to checkout specific revisions. (#16066)" (#16101)
This reverts commit 856a95f08c3674cf34edbd15cf51d4fbffe84a5c.
--
wpt-commits: fbd91b73ea03f23fffe4717556c088ae344c9501
wpt-pr: 16101
Automatic update from web-platform-tests
Part 0: Remove a bug from a meta file, and test that we aren't comparing offers with answers.
Differential Revision: https://phabricator.services.mozilla.com/D24096
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1531122
gecko-commit: ecb3fee216580948044845803338c60e3a283ffe
gecko-integration-branch: central
gecko-reviewers: jib
--
wpt-commits: 65f12c6cb3d58c8000400b76b9ab7f32961793e9
wpt-pr: 16039
Automatic update from web-platform-tests
Don't use HEAD or FETCH_HEAD to checkout specific revisions. (#16066)
FETCH_HEAD is unreliable because it's a global variable that can be
accidentially clobbered by adding an additional fetch anywhere in the
pipeline. As a result running tests in CI has been broken since we
chose the wrong revisions. HEAD is more reliable but doesn't exist
until we first check something out.
Instead, do the following:
* Fetch the initial commits into a branch called task_head and check
this out unconditionally.
* For PRs, create branches called base_head and pr_head pointing to
the two parents of the merge commit that we test on PRs.
* Express all the other revisions in terms of task_head, pr_head and
base_head, since they are both correct and more descriptive than
using complex revision specifiers.
* Move as much logic as possible out of the script baked in to the
docker image since that's hardest to update.
--
wpt-commits: 856a95f08c3674cf34edbd15cf51d4fbffe84a5c
wpt-pr: 16066
Automatic update from web-platform-tests
Upload MANIFEST.json.bz2 and MANIFEST.json.zst (#16083)
The first half of #16081.
zstandard has the best compression ratio and fast decoding. bzip2 has good compression
and very slow decoding. gzip has poor compression and fast decoding. Overall zstandard
is alway the best to download + decompress, but relies on a third party Python package.
gzip is always the worst unless network is very fast and CPU very slow. So in the future
we will move to zstandard where possible and bzip2 where not possible.
--
wpt-commits: d5921ca1198a8f3ddbecd8392c1dada9c4aa8fbc
wpt-pr: 16083
Automatic update from web-platform-tests
Fix external/wpt/event-timing/event-timing-onloadobserve.html to be more deterministic
This test passes as some events like click or mousedown for the first
click are missed at the second PerformanceObserver in startObserver.
This CL makes sure that the first PerformanceObserver does not proceed
until the first click event happens.
Actually we found the test failed when we use a different task runner is
used for WidgetInputHandler (https://chromium-review.googlesource.com/c/chromium/src/+/1530492/4).
Bug: 872081
Change-Id: I8d8fe187b8053140f40ae9cf08737fcf7b64233c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538136
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644321}
--
wpt-commits: b3689e4125b4bde0e6f90d9144726ad4689ddd6d
wpt-pr: 16051
Automatic update from web-platform-tests
[LayoutNG] Ignore cached min/max widths tainted by extrinsics.
Some properties (e.g. percentage padding) cause the cached min/max
preferred inline sizes to be affected by the extrinsic size calculation.
We store preferred min/max *border box* sizes. When a shrink-to-fit
container has percentage-based inline padding, the resolved percentage
padding is part of the preferred size. So, what we store is no longer
purely intrinsic in this case, since percentages are resolved against
something on the outside. The values need to be updated if the size of
the containing block changes. Therefore, never re-use a previously
calculated min/max preferred inline size in such cases.
Remove code from NGBlockNode::Layout() which attempted to cope with such
situations by using the legacy layout engine to recalculate min/max
values. This doesn't work, because the legacy layout engine hasn't been
updated with the new containing block size at this point (which are
needed in order to resolve percentages correctly).
Bug: 932979
Change-Id: I884bb2777babe9dae785055bac5029d7ea941a66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538085
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644319}
--
wpt-commits: c3be5b409630ad5d6c82f22e24216383dcb53426
wpt-pr: 16079
Automatic update from web-platform-tests
Remove the build_css_testsuite job
This is no longer required. It's also the final job that uses travis
for anything.
--
wpt-commits: 87f87e1276cdbf9f4af14dcb12d3d7bc1200d7c5
wpt-pr: 16086
Automatic update from web-platform-tests
Include html WebIDL in idlharness for WebRTC
It needs EventHandler to validate event handler definitions
--
wpt-commits: c92ac65812a275fd7fcfd6c8e6b68403b084b048
wpt-pr: 16046
Automatic update from web-platform-tests
Verify `Sec-Fetch-Site` is correct for domains with trailing dots.
`example.com` != `example.com.`. These are clearly distinct origins,
and we don't currently consider them to have the same registrable
domain (though there's a bit of a question about that. See
https://github.com/publicsuffix/list/issues/792), so they ought
to compare as `cross-site`
This patch adds a test for this behavior, and teaches the test harness
to resolve domains that end in `.test.`.
Closes https://github.com/mikewest/sec-metadata/issues/15.
Bug: 843478
Change-Id: Ic71afeda69f274c23c19608177756d882307a59d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536180
Commit-Queue: Mike West <mkwst@chromium.org>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644261}
--
wpt-commits: 22be9a97638436380f88d871ecefac3f1aebfe53
wpt-pr: 16036
Automatic update from web-platform-tests
HTML: move noscript test to its appropriate place
--
wpt-commits: 080f374c76435599277acbc8d7796477be5b43f4
wpt-pr: 16078
--HG--
rename : testing/web-platform/tests/html/scripting/the-noscript-element/non-html-noscript.html => testing/web-platform/tests/html/semantics/scripting-1/the-noscript-element/non-html-noscript.html
Automatic update from web-platform-tests
Close files opened in w3ctestlib (#16059)
This causes problems with PyPy as without refcounting it doesn't
close files so quickly, and you run out of file descriptors on macOS.
--
wpt-commits: 5225e2c276b7e738ef4f9dd0cf6544fa64ef06d9
wpt-pr: 16059
Automatic update from web-platform-tests
Adding OS Release and OS Build info to the run_info for Edge (#15992)
--
wpt-commits: 9925422bd502153c8cc783b4020269f7ff98c05a
wpt-pr: 15992
Automatic update from web-platform-tests
Expand/ceil default object size in SVGImagePainter
Ceil the default object size passed to LayoutImageResource::GetImage, to
increase the chances of the (container) size round-tripping through
Image::Size() (which we use as the source rect).
SVGImageForContainer::Size uses RoundedIntSize(), so depending on the
fractional part of the default object size it could end up either
smaller or larger.
Bug: 944739
Change-Id: Ifc62ddfad760ade87135b356ce6f6e07ed8e5dc5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538421
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#644238}
--
wpt-commits: b1a2ae26aa24631c3b7a81bb33a02beea21e4243
wpt-pr: 16062
Automatic update from web-platform-tests
Add tests for creating mfrac children dynamically (#16075)
* Add tests for creating mfrac children dynamically
--
wpt-commits: e5cb5a68d2b0b0491c2cf1e7a0804c5ccd9b515e
wpt-pr: 16075
Automatic update from web-platform-tests
Use GitHub actions to build manifest, tag and release.
--
wpt-commits: f67bd5cfa46f2c977305594e92e88e0db51a2050
wpt-pr: 15781
Automatic update from web-platform-tests
[Editing] Preserve inserted content's original style when inserted into an empty block
https://crrev.com/2072093002 introduced a behavior that, when content
is inserted into a block, the content's original style is removed to
match the block's style.
This results in a regression that the content's style is lost when the
block is empty and has nothing to match. Therefore, this patch preserves
the content's original style when the block is empty.
This also ensures style preservation when the insertion is an internal
operation of a higher level formatting command, e.g. outdent.
Note: this patch introduces a minor regression that, 'text-indent' CSS
property appears in a wrapper span after outdent command. This seems
harmless, though, as 'text-indent' applies only to block elements, so
the wrapper span doesn't have any effect in this case. This will be
cleaned up in a followup patch.
Bug: 818888
Change-Id: I2a6302cd5aa033339a8b857e3183dc5a2a261b4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531683
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644200}
--
wpt-commits: ee4b086658e4633927ac88f9b3a1c7f471fc5618
wpt-pr: 16069
Automatic update from web-platform-tests
Fix the lack of damage tracking for root layer position changes in BGPT.
Previous to this CL, if the position of a layer changed, and that layer
was the root layer targeting a render surface, the old location of the
surface was not damaged in the *parent* render surface. With BGPT disabled,
this was masked by transform_changed being set at [1], which triggered
the conditional at [2] and caused the old location to be damaged. With
BGPT enabled, transform_changed is never set. The new logic here detects
LayerPropertyChangedNotFromPropertyTrees() for a root layer, and
triggers the conditional at [2].
[1] https://cs.chromium.org/chromium/src/cc/layers/layer.cc?rcl=4b6a562c7bde8700fe66eda5d3f65b3e48750ef2&l=758
[2] https://cs.chromium.org/chromium/src/cc/trees/damage_tracker.cc?rcl=8c9c36220d67ee9ea6a4d830b7020cceb52e5aeb&l=449
Bug: 939282
Change-Id: I946c1d85baf7096ef6199efc811cafe55798d930
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1533176
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644099}
--
wpt-commits: 8e207ff305b5c7daad5b930a450f7ac053b1171a
wpt-pr: 16065
Automatic update from web-platform-tests
[idle] Add a threshold minimum of 60 seconds in IdleDetector
This change adds a minimum threshold of 60 seconds to prevent sites from
observing user signals such as typing cadence, or identifying users
with physical or cognitive imparments that may require more time to
interact with user agents and content.
Bug: 939883
Change-Id: I3ab19b2f7d6711c14356575d338819f501eafb9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535286
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643965}
--
wpt-commits: ea7981d4c3eb888bcc3d19b0270937c06b92e4f6
wpt-pr: 16033
Automatic update from web-platform-tests
Add references for CSS2/sec5
Some CSS2/sec5 tests were missing references. This adds in references for the remaining sec5 tests without references except for first-letter-000.xht.
--
Add in references for css/CSS2/selector tests
All CSS2/selector tests were missing references. This change adds in references for these tests.
--
wpt-commits: 2eb1f3a046ffccef07c831897f262fbcc31ec8e8, 69e5802277ed34ad99092743b4313ab8eec7323e
wpt-pr: 16061
Automatic update from web-platform-tests
Fixed some typos and mistakes in the css-text WTP test suite
Typos and formatting changes mostly, but also some errors related to the
line-height property that caused errors in Firefox.
Change-Id: Ieac66a25511dbd3386d6a737b63dfbd5e677ec2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538189
Reviewed-by: Manuel Rego <rego@igalia.com>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#643832}
--
wpt-commits: 0b2be811fa3587838fdb1399195610a176de3872
wpt-pr: 16058
Automatic update from web-platform-tests
CORS/XHR: mark Client Hints tentative
This ensures Client Hints related tests outside the client-hints/ directory are marked as tentative (and one is effectively removed as it duplicates other tests) as there's no Fetch integration anymore.
--
wpt-commits: cc011877337a36d13bdbcc9f40faab438e5ae0c9
wpt-pr: 16048
Automatic update from web-platform-tests
[css-flex][css-grid] Fix synthesized baseline
When a flex or grid container has no baseline,
its baseline should be synthesized from the border edges.
The same happens for flex and grid items.
Right now we were using the content box in some cases
and even using the margin box in a particular scenario.
The patch fixes this and update the existent tests
to the new behavior. Three new tests are added to WPT too.
At the same time this is also fixing the baseline for
inline flex/grid containers to make it interoperable with Firefox.
Inline blocks have a special behavior per legacy reasons,
which applies to inline flex/grid containers when they have no items;
otherwise the items should be used to compute its baseline.
See more at: https://github.com/w3c/csswg-drafts/issues/3416
BUG=659610,671132
TEST=external/wpt/css/css-align/baseline-rules/synthesized-baseline-flexbox-001.html
TEST=external/wpt/css/css-align/baseline-rules/synthesized-baseline-grid-001.html
TEST=external/wpt/css/css-align/baseline-rules/synthesized-baseline-inline-block-001.html
Change-Id: Ic11fbfc0a6ab9252568ea1734dcbbcbc3dbeb68c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1533952
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#643817}
--
wpt-commits: 4f3229dc2f08ccfb7463b07049df0e67d542e222
wpt-pr: 16016
Automatic update from web-platform-tests
Revert "Reland "Create RTCIceTransport using a webrtc::IceTransportInterface object.""
This reverts commit 161757587a9e4dd8089e4e648cace1575a4bec2d.
Reason for revert: I'm gonna revert this change for now because it surfaces a problem with webrtc::IceTransportInterface object lifetime that leads to crashes (see crbug/945210). Looks like the webrtc IceTransport is cleared by Jsep while the IceTransportAdapterImpl is constructed. So we have to fix the raw pointer access and provide some guarantee that the object is still alive when accessing from blink layer.
Original change's description:
> Reland "Create RTCIceTransport using a webrtc::IceTransportInterface object."
>
> This is a reland of dd0f551fcd96d46c6ec2b2a7c543cb2083f1831d
>
> Original change's description:
> > Create RTCIceTransport using a webrtc::IceTransportInterface object.
> >
> > Previously, when creating a blink::RTCIceTransport, the corresponding
> > webrtc::IceTransportInterface object was created by the
> > IceTransportAdapterImpl. However, in DTLS transport implementation, the
> > webrtc object is preexisting. Pass the preexisting webrtc object when creating
> > the blink::RTCIceTransport object in this case.
> >
> > Bug: 907849
> > Change-Id: Ia024afc101be830e30f233d6ef1bf39f141227df
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1520486
> > Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
> > Reviewed-by: Harald Alvestrand <hta@chromium.org>
> > Reviewed-by: Henrik Boström <hbos@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#642487}
>
> Bug: 907849
> Change-Id: Ib428f33faae0563d12d246bc971e38f9a66d629a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1533896
> Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
> Reviewed-by: Henrik Boström <hbos@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#643321}
TBR=hta@chromium.org,hbos@chromium.org,marinaciocea@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 907849,945078,945210
Change-Id: Ib7c5d0b8156d86e47178b757fac3d53520e56ea9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538181
Reviewed-by: Marina Ciocea <marinaciocea@chromium.org>
Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643805}
--
wpt-commits: 198031e754b9f712365466c7a5890d7f6e769ed1
wpt-pr: 16053
Automatic update from web-platform-tests
Consolidate .gitignore files under the root (#15952)
Multiple .gitignores aren't supported by the manifest update code when running
against the filesystem, so put all the rules in the root file instead.
This also adds a lint to check for extra .gitignore files.
--
wpt-commits: 46712a196fbac08bac95203f4d0861d25268ea7f
wpt-pr: 15952
Automatic update from web-platform-tests
Send `Sec-Fetch-Mode: nested-navigate` for nested navigations.
As defined in [the Fetch Metadata spec][1], the `Sec-Fetch-Mode` header
should have a value of `nested-navigate` when sending a request meant to
be committed into a nested browsing context. This patch implements that
value.
[1]: https://mikewest.github.io/sec-metadata/#sec-fetch-mode-header
Bug: 945092
Change-Id: Ibacb5bd27b7c5b17ec3d373f5d439fad2e0ac784
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536179
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643796}
--
wpt-commits: 4464a966f705350905a434690a2c98a3b4a2b0cb
wpt-pr: 16034
Automatic update from web-platform-tests
Add test to check rendering of children of mspace (#15947)
--
wpt-commits: 5d74e7772fc3b32203c5185a537c02c539bf99c6
wpt-pr: 15947
Automatic update from web-platform-tests
Fetch: make it a little clearer this list is not that special
--
wpt-commits: ad60e49e1f0e62b690760972492eb945a0c13416
wpt-pr: 16049
Automatic update from web-platform-tests
[shadow-dom] Fix flakiness of untriaged/html-elements-in-shadow-trees/html-forms/test-003.html
The test assumed to finish a form submission in 2 seconds. It's the
source of the flakiness. We should listen 'load' event of the target
iframe.
Bug: crbug.com/941565
Change-Id: I2010d1ade5240acd99030751b595ee711c71c74e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535685
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643751}
--
wpt-commits: 95dc0badd6ab33d9706372bce73c6751ce52fad1
wpt-pr: 16047
Automatic update from web-platform-tests
Active lock orientation algorithm tests
--
Fragment navigation test
--
Refactoring
--
Suggested edits
--
Add element that represents the actual fragment
--
wpt-commits: 6b4f997ddf44dfa8de0ebc32efce8bf96c87ba8c, 2efa6123606550ceb0d42151640efa8a80b3533b, 186650ff075e14ffdc8b6be4c5fa9156add7e243, de041de96601e556b6788815511fc60f8b220745, e9cad1bbdac87dc162fb662d5dca0f2cf734b831
wpt-pr: 15705
Automatic update from web-platform-tests
Add RTCSctpTransport basic state tests
Checks that SctpTransport is created, and that it reaches the connected state.
Bug: chromium:818643
Change-Id: Ifb8816e3790e36f029fe629040310c0a9229c636
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535894
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643696}
--
wpt-commits: 122a4672fa0dc554a6e7528fa3487fd907c792ee
wpt-pr: 16037
Automatic update from web-platform-tests
Data channel tests updated by Lennart Grahl <lennart.grahl@gmail.com> (#16038)
* Data channel tests modernized/updated by Lennart Grahl <lennart.grahl@gmail.com>
* Fix according Harald comments
--
wpt-commits: 0e97d09a90f8e384d0a819f9f9be2ea7e17302bb
wpt-pr: 16038
Automatic update from web-platform-tests
Add a tentative WPT test for redirect handling.
The fix added a unit test in //net. Now that the spec bug has been
filed, also add a test to WPT. Mark it tentative because it does not
actually reflect the specification, just actual browser behavior.
See https://github.com/whatwg/fetch/issues/883 and associated bug.
Bug: 942073
Change-Id: I60aeef60ec8241f483d23ec7c1fd8ce8e5949d2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1532901
Commit-Queue: David Benjamin <davidben@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643671}
--
wpt-commits: 5a8082c2179c0e6c3d3faa6fe4a85edf33b57fd7
wpt-pr: 15961
Automatic update from web-platform-tests
Portals: Add checks for failure scenarios for activate()
The promise returned by activate() rejects with an error if:
- activate() is called on a portal that is already activating
- activate() is called on a portal when another portal in the document
is already activating
- activate() is called on a nested portal
Bug: 914122
Change-Id: I43136bc363be9f710dae6c107058b7b1a6674263
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496482
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643545}
--
wpt-commits: f0aa35ac335f10c527e1fc1b30d29d5d2678f58d
wpt-pr: 15626