Automatic update from web-platform-tests
Cookie Store: Refactor tests to also work in window context.
This refactor condenses service worker test files by converting the
service worker scripts into .any.js WPT files that test both window and
worker contexts.
Change-Id: Iee64f5cc68b939ab02b06910444b8ebffdf359a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851232
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720381}
--
wpt-commits: ff11f93316527e37ec580adca01a9cf0a58a297e
wpt-pr: 20468
Automatic update from web-platform-tests
Delete invalid test. (#20547)
It seems it expects `transform: rotate(1deg, 20px, 20px)` to somehow be valid.
It was introduced in cdc3032f56c86cc68121e54e169485441d9cdb1a, pointing to https://www.w3.org/TR/css-transforms-1/#svg-transform-functions, which doesn't say anything like that.
Doesn't pass in any browser.
--
wpt-commits: 5df56b25e1cb81f81fe16c88be839f9fd538b41e
wpt-pr: 20547
Automatic update from web-platform-tests
Fix parser mXSS sanitizer bypass for <p> and <br> within foreign context
Prior to this CL, the following code:
<svg></p></svg>
parsed to this innerHTML: <svg><p></p></svg>
This is in contrast to this code:
<svg><p></svg>
which parses to <svg></svg><p></p>
The fact that the </p> is left inside the <svg> allowed sanitizer
bypasses as detailed in [1]. Please also see [2] for the spec
discussion.
With this CL, </p> and </br> within a foreign context now cause
the closing of the foreign context.
[1] https://research.securitum.com/dompurify-bypass-using-mxss/
[2] https://github.com/whatwg/html/issues/5113
Bug: 1005713
Change-Id: Ic07ee50de4eb1ef19b73a075bd83785c99f4f891
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940722
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720315}
--
wpt-commits: 561b765308e6d188618f3ba73091bb598d8357ce
wpt-pr: 20489
Automatic update from web-platform-tests
Portals: Do not create a RemoteFrame for a portal when a portal if
inserted into a disconnected node.
Bug: 1029508
Change-Id: I8d90a488198b0772baa2bd41a16c6a330fc792fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943310
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720283}
--
wpt-commits: 20bb1ca5db519ee5d37ece6492868f8a6b65a2e7
wpt-pr: 20536
Automatic update from web-platform-tests
Add ref tests for web-animation play controls
This patch adds ref tests for play controls and enables these tests to
run as part of a virtual test suite with the compositor enabled. The
tests are designed to catch regression that break animation play
controls.
Tests were added for syncing the compositor start time as well as
updating the playback rate.
The test for zero playback rate exposed a bug where it should have been
disabled on the compositor but wasn't. This bug is also fixed in the
patch.
Bug: 1029123
Change-Id: I0304d80b93ef273dd2f1dbcd58e2371bc046941e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943367
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720190}
--
wpt-commits: 995900fc628dcbfd79fb78dc816e5bea17119c84
wpt-pr: 20541
Automatic update from web-platform-tests
Fix play controls for composited animations. (#20492)
Play controls recently broke for composited animations due to timing
differences on when variables are changes. Per spec, the start time is
not cleared when pausing an animation until after the animation is
ready. This discrepancy lead to a case when PreCommit would not get
called when pausing a composited animation.
Reverse and updatePlaybackRate were also broken for composited
animations. We cannot composite infinite duration animations in the
reverse direction. We were using playback rate instead of
EffectivePlaybackRate in one of our checks for compositor eligibility,
and falling to catch this case.
Finally, with changes to when start time is cleared, we can be in a
case where it is important to preserve the start time or the current
time when starting a composited animation. Fortunately, we can
determine when start time is the important factor based in whether the
animation is pending.
Next step: Add WPT tests that would have caught the regressions. Filed
as issue 1029123.
Bug: 1028985, 1028986
Change-Id: I4edf851790a860d20962df84944558e7dbc1863a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940885
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720042}
--
wpt-commits: dfcdaf109407d4b8db06e8fbf37b2a0cb80f251f
wpt-pr: 20492
Automatic update from web-platform-tests
Remove cross fade from backgrounds
background-image-interpolation should not use cross fade. Bug filed: https://bugs.chromium.org/p/chromium/issues/detail?id=1029358
background-image-interpolation when interpolate from single image to multiple images at progress -0.3 will give from, from instead just from.
Bug filed: https://bugs.chromium.org/p/chromium/issues/detail?id=1029529
Bug: 900581
Change-Id: I481725439b8ef3944693b4c65dbc4112eca42265
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1942492
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Hao Sheng <haozhes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720267}
--
wpt-commits: c2efb44a06853e1acaf0f2cbc298399bdee28a32
wpt-pr: 20514
Automatic update from web-platform-tests
Add `Sec-Fetch-Dest: empty` header for application cache. (#20342)
`Sec-Fetch-Dest` header for both manifests and resources should be `empty` for
the requests called from application cache according to step 4 and 18.3 of
https://html.spec.whatwg.org/#application-cache-download-process:
```
4. Let request be a new request whose url is manifest URL, client is null,
destination is the empty string, referrer is "no-referrer", synchronous flag is
set, credentials mode is "include", and whose use-URL-credentials flag is set.
18.3. Let request be a new request whose url is URL, client is null,
destination is the empty string, origin is manifest URL's origin, referrer is
"no-referrer", synchronous flag is set, credentials mode is "include",
use-URL-credentials flag is set, and redirect mode is "manual".
```
Bug: 1024198
Change-Id: I6566cead95f995089685fc8eed9635d82e3d4d81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1926478
Commit-Queue: Yifan Luo <lyf@google.com>
Reviewed-by: Chase Phillips <cmp@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#719137}
--
wpt-commits: 3d59dcaa20452602f4c350f72f07ea6cf3d47e35
wpt-pr: 20342
Automatic update from web-platform-tests
Do not generate layout boxes for non-rendered foreignObject.
This change effectively re-introduces the code from [1] but only let it
affect layout tree building, not style computation, which was the reason
why the code was removed in the first place.
This also fixes the resolved style for width/height returned from
getComputedStyle() to return 'auto' for a computed value of 'auto'.
This matches the Firefox behavior.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/1070137
Bug: 1027905
Change-Id: Ie324de5b0693beea3e6626a36b25f7274234d15b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1935114
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720234}
--
wpt-commits: 42b5913b5f66ef96a6595e33cb61dba3c226c7aa
wpt-pr: 20451
Automatic update from web-platform-tests
Add test for content-dpr in pseudo-element (::after) (#20525)
--
wpt-commits: 636b9304bf7a79e25de56338b501383caf18f8ee
wpt-pr: 20525
Automatic update from web-platform-tests
[css-scroll-snap] Resnap containers after layout changes
Per spec [1], snap containers should attempt to snap after layout
changes and initial layout. If the previously snapped element still
exists after the layout change, then the container must snap to it.
This patch only considers snap targets set on the main thread since
snap targets set on the impl thread are currently not synced back to
main; this behaviour will be implemented in a follow-up.
Design doc:
https://docs.google.com/document/d/1Ufy55a19-iquba-LBiAE6AS2yBzfBQ5ZHFSpZGabS4c/edit?usp=sharing
[1] https://drafts.csswg.org/css-scroll-snap/#re-snap
Bug: 866127
Change-Id: I1442e0f464408fb5d9c49c5748a45aec0ed4d166
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912906
Commit-Queue: Kaan Alsan <alsan@google.com>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720007}
--
wpt-commits: c4182149f03eb30058efcd0e46c6e41b526f1cb1
wpt-pr: 20241
Automatic update from web-platform-tests
Remove -chunk from master branch task names
These labels are used by wpt.fyi so can't change
--
wpt-commits: 0c4e918e812f466d77e497a92048ada2d0c56383
wpt-pr: 20531
Automatic update from web-platform-tests
Reland the decision task (#20408)
A decision task is the first task run, and ensures that we only
schedule subsequent tasks which are relevant to the current push or
pull request. This dynamic scheduling helps reduce load since we avoid
spinning up workers for tasks that ultimately don't run, and unlocks
new possibilities since we are able to schedule tasks that are
dependent on other tasks.
The tasks, their scheduling criteria and their dependnecies are
specified in a a YAML format configuration file in
tools/ci/tc/tasks/test.yml. This has a bespoke format, adopting some
ideas from Azure and Gecko's taskcluster integration. The format is
documented in `tools/ci/tc/README.md`. The data in that file undergoes
trandformations to produce a set of tasks, which are then filtered
according to the event that caused the decision task to run.
To initially prove out the implementation of dependent tasks we make
the Firefox tasks depend on a download task. But this does not yet
include the work to actually make the dependent tasks download Firefox
from the parent task.
--
Add missing --test-type argument to run_taskcluster
--
Add a hack to support the old run_tc syntax
This helps avoid needing to rebase old PRs
--
wpt-commits: 54bbfc787ff480f05396251abd1ef522b3a053e4, 09774ed0396773fb57aa973ee4d115f1b2cdf23a, 8e175af1b2917b10942077d4609947937db71b92
wpt-pr: 20528
--HG--
rename : testing/web-platform/tests/tools/taskcluster/testdata/master_push_event.json => testing/web-platform/tests/tools/ci/tc/testdata/master_push_event.json
rename : testing/web-platform/tests/tools/taskcluster/testdata/pr_event.json => testing/web-platform/tests/tools/ci/tc/testdata/pr_event.json
Automatic update from web-platform-tests
[css-pseudo] Properly check that ::marker supports text-combine-upright
The marker-supported-properties.html test was checking that the
'text-combine-upright' property can be set to 'none' in ::marker.
However, this wasn't much useful, since 'none' is the initial value.
The test would pass even if ::marker ignored the declaration.
Change it to check 'text-combine-upright: all' instead.
Bug: 457718
Change-Id: Ib3b2109713f474e2fc75918184795036e1fea664
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943239
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#720174}
--
wpt-commits: 87d3a057ba2a82aaf19eecad4b11d1ecd4f1aad1
wpt-pr: 20529
Automatic update from web-platform-tests
Service Worker: Add tentative wpt test for FetchEvent WorkerTiming in frame
This patch adds tentative wpt test. Currently FetchEvent WorkerTiming is a
tentative feature. In chromium, this feature hasn't implemented completely yet,
so some tests will be failed.
Explainer : https://github.com/wanderview/fetchevent-worker-timing/blob/master/explainer.md
Bug: 900700
Change-Id: I7a43989d8833ddd65c93106de67c4ebe6bd9ed52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1915644
Commit-Queue: Yuta Kasai <yutakasai@google.com>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720134}
--
wpt-commits: 02fd77cbb9306cadf642fbc0e4637f22d949a8c0
wpt-pr: 20471
Automatic update from web-platform-tests
[webnfc] Add test for multi scan from the same NDEFReader object
This CL adds a test for testing multiple scan() from the same
NDEFReader object with new options should replace existing filters.
Test fails at present as which has not been implemented yet.
This CL also rename NDEFReader_options.https.html as
NDEFReader_scan_filter.https.html because NDEFReader has no
construct options any more, and this test file is mainly for
scan filter testing.
BUG=520391
Change-Id: I4d19659c990c0ddc8dc19a5984c55be1ece48e9c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1939327
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Leon Han <leon.han@intel.com>
Cr-Commit-Position: refs/heads/master@{#720112}
--
wpt-commits: cc2a1d047aa0e6d9a4eb8231e2fa9d0fb34cbe9e
wpt-pr: 20474
Liang-Heng Chen
moz-wptsync-bot
James Graham
Staphany Park
Emilio Cobos Álvarez
Florian Rivoal
Mason Freed
Morten Stenshorne
Lucas Furukawa Gadani
Kevin Ellis
Blink WPT Bot
haozhe
autofoolip
Rune Lillesveen
Noam Rosenthal
Ian Clelland
Kaan Alsan
jugglinmike
Oriol Brufau
Yuta Kasai
Wanming Lin
Stephen McGruer
Philip Jägenstedt