Automatic update from web-platform-testsMake sync-tests.sh work with git.
--
Allow specifying the mozilla tree via argument.
--
wpt-commits: 8b61c282650bf72bce0147df320425343ea27f2f, e639f5b4158852b16ffa28613730c2b0b63f5e83
wpt-pr: 11715
Automatic update from web-platform-testsSync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/6041c030780420b6205cf2d6640513606609884c
This contains two changes:
* One by Mihir Iyer from [bug 1398483](https://bugzil.la/1398483), reviewed by
@dholbert, adding flexbox column-{row,gap} reftests.
* One by myself from [bug 1464782](https://bugzil.la/1464782), replacing the
usage of offset-* logical properties by the standard name inset-*, reviewed
by @upsuper.
--
wpt-commits: dc302574be5e27db4ade270698c966a39a09e300
wpt-pr: 11714
Automatic update from web-platform-testsUpdate external/wpt/webrtc/RTCRtpParameters* tests.
This is in preparation for get/setParameters[1] and
RTCRtpTransceiver[2].
Tests are updated to use promise_test and async/await to make them
easier to write and to execute sequentially.
Tests are updated to set up a call before getParameters() because many
parameters are defined as "that has been negotiated". If we want to test
what is returned before negotiation we should add that as separate
tests. For now, this is necessary for the tests to run on [1][2].
Some tests are removed because they no longer reflect the spec.
Because get/setParameters() and RTCRtpTransceiver has not landed yet,
the tests are still expected to fail.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/1102436
[2] https://chromium-review.googlesource.com/c/chromium/src/+/1025771
Bug: 803494, 777617
Change-Id: I3f14a37925837576a602d91bb67e48181c56a946
Reviewed-on: https://chromium-review.googlesource.com/1102502
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571430}
--
wpt-commits: 36fb033a4051e63a0ab4bd073fdaadf808953564
wpt-pr: 11526
Automatic update from web-platform-testsUpdate links to feature policy documentation.
The documentation in the Feature Policy spec repository was moved to the
'master' branch from the 'gh-pages' branch. This updates several
references in the Chromium codebase with the new locations.
TBR=kinuko
To-be-reviewed-by: kinuko@chromium.org
Bug: 857055
Change-Id: I10b4c55608a218b1767a4990832d86e460cd37d5
Reviewed-on: https://chromium-review.googlesource.com/1116868
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570906}
--
wpt-commits: d60079a316ee35415d426ed5a2e8c0574efca80c
wpt-pr: 11687
Automatic update from web-platform-testsMark a vertical-scroll test as 'slow'
The test has been previously disabled (skipped) on Windows due to
recurrent timeouts. Running the test locally leads to an average of ~
3.7 sec runtime on a high-performance Windows 10 rig (Z840). The test is
not skipped on Linux right now, but since its runtime exceeds the 2 sec
rule of thumb (from the comments in SlowTests), this CL will make it
slow on Linux as well.
Bug: 850964
Change-Id: Ib478c0f59313da4302325578d9b768e1070bdcb6
Reviewed-on: https://chromium-review.googlesource.com/1115214
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571116}
--
wpt-commits: fdc6e085458e80d3bfccfe59dc47adc7dd14bc45
wpt-pr: 11690
Automatic update from web-platform-tests[LayoutNG] bugfix for NG painting in vertical-rl with scrollbars.
This bug occurs when painting NG child inside non-inline vertical-rl parent
with scrollbars.
Root cause is extra scrollbar offset that Paint applies to Legacy painting that
is not needed for NG.
The fix is hacky: NG applies reverse offset.
This fix does not make any additional tests pass or fail.
Bug: 852395
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: I7dda2cdbf682485ab30c048987ae683981731886
Reviewed-on: https://chromium-review.googlesource.com/1115863
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571080}
--
wpt-commits: e7aa3025a97a793b4fe5776dcf616f6e845d1ce0
wpt-pr: 11703
MozReview-Commit-ID: JlUogtQDeVU
Automatic update from web-platform-tests[LayoutNG] Non-"inline" abspos needs to ignore floats and text-indent.
This fixes two tests, but will also eventually benefit
floats-wrap-inside-inline-00[1234].htm in fast/block/float/, which are
currently passing because the absolutely positioned box in the test forces
its container to have block children. There's special-code for NG (which we
should remove) in LayoutBlockFlow::AddChild() that forces this (and causes
other problems).
Added a new test, to make it clear what this fix is about.
Bug: 734554
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: Ia2c0e0b2ab61999207114fdf935880fabc2e677c
Reviewed-on: https://chromium-review.googlesource.com/1116959
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571054}
--
wpt-commits: 12b9b4c9d40504a6d5df9339d7680a8a89184f18
wpt-pr: 11697
MozReview-Commit-ID: 9VzFxid8Ry8
Automatic update from web-platform-testsAsync Cookies: Implement sameSite attribute.
This CL modifies RestrictedCookieManager to allow renderers to set the
SameSite and Priority CanonicalCookie attributes. Renderers must be
allowed to set the SameSite and Priority attributes so that
RestrictedCookieManager can be used to implement the document.cookie
setter.
Bug: 856364, 729800
Cq-Include-Trybots: luci.chromium.try :linux_mojo
Change-Id: Ic0a520bc6c02c259ef22175c9eb161086fa18782
Reviewed-on: https://chromium-review.googlesource.com/1115586
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570976}
--
wpt-commits: 5392b81b526e3e0bbe805f1407a235d640f879a5
wpt-pr: 11696
MozReview-Commit-ID: 8dBERNSQC7I
Automatic update from web-platform-testsMove AudioBufferSourceNode tests to WPT
These tests basically pass on Firefox. If they don't, it's because
Firefox is incorrect and issues have been filed for these.
During the testing, we discovered that an incorrect assumption was made
that calling start() would always work. Because of test failures in Firefox,
this assumption is incorrect.
Updated audit.js to latest Chrome version (to get loadFileFromURL) and
add wpt lint exception for a console message in audit.js.
Needed to update audiocontext-getoutputtimestamp.html to make bots happy
because the AudioContext is running now on the bots, so time is
progressing, so the time stamps aren't always zero.
Bug: 745778
Change-Id: I5f9ee01498678db0feb57051f682772ca7bd9fbb
Reviewed-on: https://chromium-review.googlesource.com/1040865
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570890}
--
wpt-commits: 4d9bf95859072bac1680dff77c81cb640db6a6a5
wpt-pr: 10830
Automatic update from web-platform-tests[wptrunner] Correct profile installation for Fx 61 (#11693)
Extend the profile installation logic to account for a transitional
phase in the format of the Firefox profile directory. More detail is
available at:
https://bugzilla.mozilla.org/show_bug.cgi?id=1471419
--
wpt-commits: 4a983bf597c9120959bab2cc4f84b29c72501037
wpt-pr: 11693
Automatic update from web-platform-testsFix the clicked iframe in two wpt fullscreen tests.
With User Activation v2, activating a parent frame doesn't activate
its subframes. We fixed these two tests by sending the click to
subframes. This needed a workaround in auto-click.js because
the mutation observer there in doesn't seem to work when a button
element is added to a subframe.
Bug: 802371
Change-Id: I786668c87b802565e99ad16223cafc8ac1fd6296
Reviewed-on: https://chromium-review.googlesource.com/868323
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570778}
--
wpt-commits: b0f0ef9adb50765ea38be619015bb061d6a224b6
wpt-pr: 11678
Automatic update from web-platform-tests[WebAudio] throw an error when buffer has been already set.
should throw an InvalidStateError when buffer has been already
set in ConvolverNode
Bug: 709656
Change-Id: Ia0826f9ffa2e180da1311f4cded8ff7fe5461147
Reviewed-on: https://chromium-review.googlesource.com/1077713
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com>
Cr-Commit-Position: refs/heads/master@{#570767}
--
wpt-commits: b44c26506446c1d95c644786254774255a96ffc1
wpt-pr: 11239
Automatic update from web-platform-testsAdd test for the removal of trailing spaces when preceding <br>
Blink and WebKit fails to remove trailing spaces preceding
`<br>`. This patch adds a test for that case. Gecko, Edge, and
the current build of LayoutNG passes this test.
This was originally reported at http://crbug.com/40634. It
turns out that fast/text/emphasis-overlap.html relies on this
behavior. Before removing the reliance, adding this test to
ensure this case is covered and to prevent regressions in
LayoutNG.
TBR=eae@chromium.org
Bug: 40634
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: Iff877bac1c27c8689bdbc6949d01a9ea380463bd
Reviewed-on: https://chromium-review.googlesource.com/1116622
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570744}
--
wpt-commits: 2a423b054124f73b1d71eba4f782c7ff4a343898
wpt-pr: 11684
MozReview-Commit-ID: LqVXYAqe2Yq
Automatic update from web-platform-testsStart running wptserve/serve tests on Py3 (#11669)
While this may seem pointless when almost all of them are marked as
xfail on Py3, it does at least mean we have to keep them importable
and should mean we don't regress code that currently works on Py3.
--
wpt-commits: a8d56dbac2ef9be373868b2f2fd2302cc522ffab
wpt-pr: 11669
Automatic update from web-platform-testsLoosen assumptions so actual implementations match them (#11677)
--
wpt-commits: 865d9b467e226e3c69d7cc1eee7849dca0973eee
wpt-pr: 11677
Automatic update from web-platform-testsRefactor and split up quirks tests
The unitless-length test was a flaky timeout in chromium.
https://bugs.chromium.org/p/chromium/issues/detail?id=646133
--
wpt-commits: cea6203ed144fd0dd4abdfd28435ddfc5404c8e0
wpt-pr: 11641
Automatic update from web-platform-tests[encrypted-media] Add segmented clear-to-encrypted test. (#11308)
This adds a test that tests transitioning from clear to encrypted
content when it appears in different segments. This can happen when
streaming and the first content is a clear ad and the encrypted content
will be appended later.
This kind of content wasn't playable on Firefox until recently and I
think this wouldn't work on Edge if they supported clear-key.
https://bugzilla.mozilla.org/show_bug.cgi?id=1454630
--
wpt-commits: f240b8f22eea1a0fbff0fe48225973775b1524c3
wpt-pr: 11308
Automatic update from web-platform-testsShadow DOM: Run the next test even if the current fails
Part of #11269.
--
wpt-commits: 829ef55855b3b3c971fb3a16b8e34961675cb9d0
wpt-pr: 11332
Automatic update from web-platform-testsThe hashchange event should not bubble
This brings the `html/browsers/browsing-the-web/scroll-to-fragid/004.html` test up to date with the spec change made here: https://github.com/whatwg/html/pull/3737.
Other tests were changed to reflect this in https://github.com/web-platform-tests/wpt/pull/11355.
--
wpt-commits: 3aaef8d2cac4ab2044a1ba01895f2e028b91d996
wpt-pr: 11672
Automatic update from web-platform-testswebkit: GTK port should whitelist the web-platform.test host certificate (#11615)
For testing purposes, the TLS certificate for the web-platform.test
host should be whitelisted for the GTK port of WebKit in order to
avoid TLS errors when loading test cases via HTTPS.
This is done by listing the host and certificate file path pair in
the port-specific capabilities. This pair is then used for
whitelisting the certificate for the given host in the
WebDriver-automated browsing session.
--
wpt-commits: cc6c95d405d3a89ace8a0565a04eee23e24af814
wpt-pr: 11615
Automatic update from web-platform-testsImplement Element.toggleAttribute
Add a new method Element.toggleAttribute(string qualifiedName,
optional bool force) that allow toggling the existence of an element’s
attribute, similar to Element.classList.toggle.
Spec
https://dom.spec.whatwg.org/#dom-element-toggleattribute
Intent to Implement and Ship
https://groups.google.com/a/chromium.org/d/msg/blink-dev/mAWBTaANvmE/OgaCRH04BAAJ
Bug: 854960
Change-Id: Iab8a1a97dd4e2f8b377bcf590401699f9013aa8a
Reviewed-on: https://chromium-review.googlesource.com/1111761
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570348}
--
wpt-commits: 0a3e5fa627dea7491d71edd1804989588bf0e498
wpt-pr: 11655
Automatic update from web-platform-testsAdd a layout test for redirects with referrer-policy via service worker
Redirects with referrer-policy header need to respect a new referrer
policy. This tries to check if it's working when the request is in a service
worker's scope.
Bug: 855948
Change-Id: Icb923fa8b8345c128f02c41e042775ba5bf499ad
Reviewed-on: https://chromium-review.googlesource.com/1113171
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570298}
--
wpt-commits: cf4a6e91f11be647a513a3f874e43f8d5a7dcd82
wpt-pr: 11654
Automatic update from web-platform-testsAllows panning inside overflowing snap areas.
According to the spec[1], if an overflowing snap area covers the
snapport in one axis and the distance between the previous snap
position and the next snap position is larger than the size of the
snapport, the current scroll position is a valid snap position.
This patch also rewrites the data structure of SnapAreaData and
SnapContainerData so that they only keep the rect and calculate the
snap points, visible region, overflow condition only when scroll
occurs.
[1] https://drafts.csswg.org/css-scroll-snap-1/#snap-overflow
Bug: 826359
Cq-Include-Trybots: luci.chromium.try :android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Iec1ebe48abe8d2653128ac2af4e6137a14c05502
Reviewed-on: https://chromium-review.googlesource.com/1075558
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570255}
--
wpt-commits: 83c33634aaf8495aa9acfe40e4612c242c45c184
wpt-pr: 11383
MozReview-Commit-ID: JmozXZZQzzx
Automatic update from web-platform-testsCSS: transform-origin does not accept top <length>
Spec:
https://drafts.csswg.org/css-transforms/#propdef-transform-origin
Blink no longer accepts transform-origin 'top 1px'. We previously
parsed it as 'top center 1px'.
Edge/Firefox/WebKit already reject such values.
BUG=855787
Change-Id: I8ac8745d41c867a2ef659ce9afe17143d60a1806
Reviewed-on: https://chromium-review.googlesource.com/1112883
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570139}
--
wpt-commits: 69a3483d7a05abb72161096baf204b37be7cc098
wpt-pr: 11635
Automatic update from web-platform-testsReland "[CSS Env Vars] Add some WPT tests"
This is a reland of 981a543f9e743001a6e492a006873de3a5953747
This adds a bugfix that adds a DetachFromParent method that
we call in StyleEngine. This stops the global environment
variables instance holding a reference to the document
one after the document has been disposed.
Original change's description:
> [CSS Env Vars] Add some WPT tests
>
> Adds some WPT tests to test env() with @supports as well
> as fallback values.
>
> BUG=825890
>
> Change-Id: I071f5c2582f8056fe39b4a50ab62140d579c577d
> Reviewed-on: https://chromium-review.googlesource.com/1111023
> Reviewed-by: Rune Lillesveen <futhark@chromium.org>
> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
> Commit-Queue: Becca Hughes <beccahughes@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569852}
Bug: 825890
Change-Id: If828b977d62145fb1ea9bb710a48d76307a054d5
Reviewed-on: https://chromium-review.googlesource.com/1113877
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570117}
--
wpt-commits: 775bb3b7bf1e28c58d8381422e6755c3f6936b46
wpt-pr: 11658
Automatic update from web-platform-testsRevert "Move a test for min-content for a soft-hyphen to wpt"
This reverts commit d37409a17a223249ee661ae504def53bf51b4ce9.
Reason for revert: external/wpt/css/css-sizing/min-content-soft-hyphen-001.html failed on Windows 10
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Win10/36928
Original change's description:
> Move a test for min-content for a soft-hyphen to wpt
>
> This tests when the inline-size is [min-content]:
> * A `­` produces a break opportunity when computing the
> min-content inline size.
> * The hyphen character generated by `­` is included into
> the min-content inline size.
>
> Originally developed in [CL:1111895].
>
> [min-content]: https://www.w3.org/TR/css-sizing-3/#valdef-width-min-content
> [CL:1111895] https://chromium-review.googlesource.com/c/chromium/src/+/1111895
>
> Bug: 636993
> Change-Id: Ib492b2db023a5169247ca00e5b745e42ec33d197
> Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
> Reviewed-on: https://chromium-review.googlesource.com/1113085
> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#570066}
TBR=cbiesinger@chromium.org,kojii@chromium.org
Change-Id: I3fb91c7c2d66e775a12994734a14afc566d05a3e
No-Presubmit: true
No-Tree-Checks: true
No-Try : true
Bug: 636993
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Reviewed-on: https://chromium-review.googlesource.com/1113667
Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570109}
--
wpt-commits: ce2196e7a345f209ce095ec6c7356f3a6cf168d4
wpt-pr: 11660
MozReview-Commit-ID: A5fo6hI5Szs
Automatic update from web-platform-testsMove a test for min-content for a soft-hyphen to wpt
This tests when the inline-size is [min-content]:
* A `­` produces a break opportunity when computing the
min-content inline size.
* The hyphen character generated by `­` is included into
the min-content inline size.
Originally developed in [CL:1111895].
[min-content]: https://www.w3.org/TR/css-sizing-3/#valdef-width-min-content
[CL:1111895] https://chromium-review.googlesource.com/c/chromium/src/+/1111895
Bug: 636993
Change-Id: Ib492b2db023a5169247ca00e5b745e42ec33d197
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Reviewed-on: https://chromium-review.googlesource.com/1113085
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570066}
--
wpt-commits: cb5379322c3ae9f1fb203d6c0b9bc12e7f6af44d
wpt-pr: 11656
MozReview-Commit-ID: 9e7iLpwrmWG
Automatic update from web-platform-testsMerge pull request #11653 from mrego/contain-size-image-alt
[css-contain] Add alt on image at contain-size-013.html
--
wpt-commits: 9d5ca975b959ed3458bd585ff53e705c0551eb62
wpt-pr: 11653
Automatic update from web-platform-testssensors: Yield to the event loop in GenericSensorTestChromium.reset() (#11625)
Do so there instead of in `MockSensorProvider.reset()`, which is now a
regular function.
This brings the code more in line with Blink's own `sensor-helpers.js`, and
fixes one of the issues described in #10906: when a test failed, we'd end up
with the following code path
1. `sensor_tests()`'s calls `GenericSensorTestChromium.reset()`
2. `GenericSensorTestChromium.reset()` calls `MockSensorProvider.reset()`
3. This function `await`s on a promise that resolves inside `setTimeout()`
and yields control back to the event loop
4. The next test is run, and it fails because
`GenericSensorTest.testInternal` hasn't been reset yet.
5. After all tests run, we go back to the `setTimeout()` callbacks and
finish running `GenericSensorTest.reset()`.
which essentially caused all subsequent tests to failure because
`1initialize()` would complain `reset()` had not been run.
We now simplify things, and a test failure results in:
1. `sensor_tests()`'s calls `GenericSensorTestChromium.reset()`
2. `GenericSensorTestChromium.reset()` calls `MockSensorProvider.reset()`,
which runs synchronously and where we close the mojo binding and stop the
mojo interceptor
3. This function `await`s on a promise that resolves inside `setTimeout()`
and yields control back to the event loop to let the mojo shutdown
process finish. The next test may start running before this `sensor_test`
fully finishes, but it's not a problem since we're not running anything
after calling `GenericSensorTestChromium.reset()`
4. The next test runs as expected because `testInternal` has already been
reset
With this change, running `wpt run` with a recent Chromium master build on
accelerometer, generic-sensor, geolocation-sensor, gyroscope, magnetometer
and orientation-sensor yields 249 failures, down from 286.
--
wpt-commits: cc0999e09fac71d8c708445cc9986ee489d12cdb
wpt-pr: 11625
Automatic update from web-platform-testsFetch: split up fetch/api/request/request-keepalive-quota.html
Part of #11571.
--
wpt-commits: f17d9eef1f6b47edc2a6872cff3a53ceceb576b6
wpt-pr: 11593
Automatic update from web-platform-testsES Modules: Use an appropriate referrer policy for module script loading
This CL fixes ReferrerPolicy handling in module script loading. Before this CL,
FetchClientSettingsObjectSnapshot's referrer policy is used, but this is wrong.
The spec requires to use ScriptFetchOptions' referrer policy.
// The "set up the module script request" algorithm:
"Set request's cryptographic nonce metadata to options's cryptographic nonce,
..., and its referrer policy to options's referrer policy."
https://html.spec.whatwg.org/multipage/webappapis.html#set-up-the-module-script-request
Specifically, this CL introduces |referrer_policy_| field in ScriptFetchOptions
class as spec'ed and propagates it to the entire path of module script loading.
ScriptFetchOptions's referrer policy can be set to following values:
- <script>'s "referrerpolicy" attribute is used for <script type='module'>. This
hasn't been implemented yet (see https://crbug.com/841673), so the current
document's referrer policy is used to keep the backward compatibility.
// The "prepare a script" algorithm:
"20. Let referrer policy be the current state of the element's referrerpolicy
content attribute."
"22. Let options be a script fetch options whose cryptographic nonce is
cryptographic nonce, ..., and referrer policy is referrer policy."
https://html.spec.whatwg.org/multipage/scripting.html#prepare-a-script
- <link>'s "referrerpolicy" attribute is used for modulepreload.
// The "Link type "modulepreload"" algorithm:
"9. Let referrer policy be the current state of the element's referrerpolicy
attribute."
"10. Let options be a script fetch options whose cryptographic nonce is
cryptographic nonce, ..., and referrer policy is referrer policy."
https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload
- The default referrer policy is used for module workers and worklets. This is
the reason why this CL changes test expectations of workers and worklets.
// The "fetch a module worker script graph" algorithm:
"2. Let options be a script fetch options whose cryptographic nonce is the
empty string, ..., and referrer policy is the empty string."
https://html.spec.whatwg.org/multipage/webappapis.html#fetch-a-module-worker-script-tree
Change-Id: Ic0f9e6667cd1b84f74d86fcc948451c1d2f8191f
Bug: 842553, 855963
Reviewed-on: https://chromium-review.googlesource.com/1111743
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569967}
--
wpt-commits: 50b0943d82d36bb92977002bebd5a7990e0ed388
wpt-pr: 11626
Automatic update from web-platform-testswebdriver: remove ES6 constructs from WebDriver tests for IE support (#11637)
IE does not support array destructuring in a `let` statement. This commit
allows the newly added element_click tests to run on IE 11.
--
wpt-commits: f9d0147b58f595f23afb6f66326745e96e105e07
wpt-pr: 11637
Automatic update from web-platform-testsUpdate Web Platform Tests for Feature Policy integration into HTML spec.
Change-Id: Ibfcc3e8bc217aff8782d2aec4c1b73bb4a193e1e
Reviewed-on: https://chromium-review.googlesource.com/1053106
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569778}
--
wpt-commits: a5facbd6fb610d896eabffbebb45da59edfbff13
wpt-pr: 10966
Automatic update from web-platform-tests[css-grid] Fix positioned items in a grid with calc() gutters
In r543079 we added support for calc() in grid gutters.
In that patch we modified LayoutGrid::GridGap() but we forgot
to do the same in LayoutGrid::AvailableSpaceForGutters().
This patch just changes the IsPercent() call by IsPercentOrCalc()
that way calc() gutters are considered too when looking
for the available space.
BUG=816300
TEST=external/wpt/css/css-grid/abspos/grid-positioned-items-gaps-002.html
TEST=external/wpt/css/css-grid/abspos/grid-positioned-items-gaps-002-rtl.html
Change-Id: I3237d5dc73f508cea6d904b9f1fd3822bb9efe55
Reviewed-on: https://chromium-review.googlesource.com/1112237
Reviewed-by: Sergio Villar <svillar@igalia.com>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#569733}
--
wpt-commits: 95c2419892175edc877e24672d8bafb8df28cfdd
wpt-pr: 11629
Automatic update from web-platform-tests[css-tables] Make scrollbars visible on mac screenshots
wpt.fyi showed Safari passing these recently-added tests because the
scrollbars don't show in either the tests or their refs.
https://wpt.fyi/css/css-tables/height-distribution/percentage-sizing-of-table-cell-replaced-children-001.html
Aside:
Edge matches Safari's current and Chrome's previous behavior. But
they've confirmed it's a bug:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/17505131/
Firefox has a mostly-unrelated incompatibility that doesn't allow us to
check it.
Bug: 837408,838144
Change-Id: I82058d3c22d7668711e9a9a1c977047033d64b46
Reviewed-on: https://chromium-review.googlesource.com/1054770
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569698}
--
wpt-commits: 644c41319451e14d31430f659c00bda948ab078e
wpt-pr: 10959
Automatic update from web-platform-testsCorrectly resolve relative URLs for registered custom properties.
Relative URLs in registered custom properties must resolve against the
base URL of the originating stylesheet. For instance, consider a style-
sheet at /style/mystyle.css:
--foo: url("myimage.jpg");
And a document at /index.html:
<style>
background-image: var(--foo);
</style>
If the property --foo is registered with syntax <url>, then the background-
image should be /style/myimage.jpg.
This is contrary to non-registered properties, in which case the
background-image would be /myimage.jpg.
To implement this, this patch scans for URL tokens and 'url('-function
tokens after (var-)resolving the registered custom property
(see CSSVariableResolver::ResolveCustomProperty). The token containing
the relative URL is then rewritten (in-place) to contain an absolute URL
instead.
To avoid doing unnecessary work, we only scan the token stream if
CSSVariableData::needs_variable_resolution_ is set. This is set either
if needs_url_resolution_ is set (because var-references could produce
relative URLs), or if the token stream contains URL/function-tokens.
When a resolved CSSVariableData is created (::CreateResolved), it is
assumed that the incoming token stream contains no URLs that need to be
resolved.
R=futhark@chromium.org, timloh@chromium.org
Bug: 851490
Change-Id: I25b1e839fc92eb538f30670fe91fc92a1ad9d5ea
Reviewed-on: https://chromium-review.googlesource.com/1109975
Commit-Queue: Anders Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569663}
--
wpt-commits: 372c7ad36a7e42a89228aa2bb88b35da5f519fa5
wpt-pr: 11611
Automatic update from web-platform-tests[css-contain] Size containment replaced elements intrinsic size is zero
The spec is very clear about this
(https://drafts.csswg.org/css-contain/#containment-size):
"Replaced elements must be treated as having an intrinsic width
and height of 0."
The patch modifies LayoutReplaced::ComputeIntrinsicSizingInfo()
so that it returns zero for elements with "contain: size".
BUG=853441
TEST=external/wpt/css/css-contain/contain-size-013.html
Change-Id: I91490b120a110be20a91d564da4fdc3d9a11b70a
Reviewed-on: https://chromium-review.googlesource.com/1110819
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#569610}
--
wpt-commits: 46c8d39a9fde254df3398c681fd724990d289892
wpt-pr: 11622
Automatic update from web-platform-testsCompleted 'unsafe-hashes' per spec
'unsafe-hashed-attributes' renamed to 'unsafe-hashes'
'unsafe-hashes' matches style attributes correctly now
'unsafe-hashes' works for javascript: URLs
'unsafe-hashes' tests added and ammended
spec (approved and to be submitted at the same time as this CR):
https://github.com/w3c/webappsec-csp/pull/311
I2I: https://groups.google.com/a/chromium.org/d/msg/blink-dev/4dohVXDfEI4/tO6rhuv4AwAJ
Bug: 771922
Change-Id: I018cc0f73d492cb4057ff4c41d9be4df8438036c
Reviewed-on: https://chromium-review.googlesource.com/1095217
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569593}
--
wpt-commits: fb04aed6ac840bd35178406583af6da6759c3566
wpt-pr: 11457
Automatic update from web-platform-testsSec-Metadata: Strings are quoted in structured headers.
So this patch adds quotes.
See https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-06#section-3.7
and 98f7c1253e.
Bug: 843478
Change-Id: I29dfa3a87e3c65a1b64009e173faa6d0f41b40f4
Reviewed-on: https://chromium-review.googlesource.com/1109819
Commit-Queue: Mike West <mkwst@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569554}
--
wpt-commits: d6020b4e6f97afaa89624f316611061673eb3f53
wpt-pr: 11605
Automatic update from web-platform-tests[testharness.js] Get title from the filename or a META comment if not given (#11403)
--
wpt-commits: f777ec99a11d0d0522e691a8dab93c70d70941f3
wpt-pr: 11403
Automatic update from web-platform-testsWPT: Add long timeout to service-worker/navigation-redirect.https.html test.
This test is slow because it does a lot of navigations.
Bug: 854913
Change-Id: I2b5f984ba4b656af0d735b3c2c14952fdac5867b
Reviewed-on: https://chromium-review.googlesource.com/1111493
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569544}
--
wpt-commits: 91c59efbec2e393f48c9983b5c84acc1aa55efd5
wpt-pr: 11620
Automatic update from web-platform-testsMerge pull request #11619 from frivoal/css-ui-11598
[css-ui] Fix paths to work in testharness & css built test suites
--
wpt-commits: 7d60038cac3d6104be86868a62892e8d1968ddc0
wpt-pr: 11619
--HG--
rename : testing/web-platform/tests/css/css-ui/parsing/resources/parsing-testcommon.js => testing/web-platform/tests/css/css-ui/parsing/support/parsing-testcommon.js
Automatic update from web-platform-testsPrevent abort error from breaking test in FF (fixes#10792)
--
wpt-commits: bbe3411e20381f494983c3acf359bb9fdcaaa16d
wpt-pr: 11614
Automatic update from web-platform-testsMerge pull request #10913 from Tavmjong/paint-context
Add basic tests for context fill and stroke.
--
wpt-commits: e3173905464f0afb36163fa271ff01957eedec7c
wpt-pr: 10913
Automatic update from web-platform-testsRemove unneeded WebAudio IDL tests
The IDL tests in the subdirectories aren't really needed anymore since
we have webaudio/idlharness.https.html that covers everything in the
individual tests.
Bug: 854220
Change-Id: I589f4972922dfc15c475ce20e7c4cb664b529920
Reviewed-on: https://chromium-review.googlesource.com/1107120
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569280}
--
wpt-commits: 1e174dd99ca9c17829565042d276ba477de5b6bc
wpt-pr: 11580
Automatic update from web-platform-testsAdd the shape-detection-api IDL file and test (#9832)
--
wpt-commits: 3f54c291ef98b8657ac772b04822460865cd6e7e
wpt-pr: 9832
Automatic update from web-platform-testsUpdate existing WebUSB WPT to be multi-global
This change updates the remaining WebUSB web platform tests to be
multi-global so that the API is also tested in the worker contexts.
Bug: 841510
Change-Id: I9df24f1ae4289ab742db275c34552200bb477b22
Reviewed-on: https://chromium-review.googlesource.com/1089033
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565778}
--
wpt-commits: a82a385bd794d9120b0eb8b94f452d4d38bfe04b
wpt-pr: 11384
Automatic update from web-platform-testsReland "Multi-global WebUSB WPT for window and worker"
This is a reland of 1ff37758f07612906228581dbc808df4b282e250
Original change's description:
> Multi-global WebUSB WPT for window and worker
>
> This change updates the existing web platform tests for WebUSB to use
> multi-global tests to test the API in the supported contexts. The
> change updates the following tests:
> * idlharness
> * usb
> * usbConnectionEvent
>
> Bug: 841510
> Change-Id: I6b118aa4121109cd6a48054c2ebc69b831660afc
> Reviewed-on: https://chromium-review.googlesource.com/1087209
> Reviewed-by: Reilly Grant <reillyg@chromium.org>
> Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#564981}
Bug: 841510
Change-Id: Ie354fdd54a4cd94a4801ee634c8d3263e0aa6e93
Reviewed-on: https://chromium-review.googlesource.com/1089647
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Reviewed-by: Chong Zhang <chongz@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567290}
--
wpt-commits: 6dee65cf657cfc5b2ad1042f778980eef79dd67d
wpt-pr: 11391
--HG--
rename : testing/web-platform/tests/webusb/resources/usb.serviceworker.js => testing/web-platform/tests/webusb/usb.serviceworker.js
Automatic update from web-platform-testsHTML: split up meta refresh parsing test
Part of #11571.
--
wpt-commits: a9d0ad0cd520582ba102993460cd318cccd8153d
wpt-pr: 11607
Automatic update from web-platform-testsWebSocket: only test 2 connections in websockets/constructor/014.html
Part of #11571.
--
wpt-commits: 7e77da661fc920d3cda671be9804fcd8a24dae29
wpt-pr: 11606
Automatic update from web-platform-testsHTML: Expect salvegable to be set to false for pagehide test
Also rename the manual test.
Part of #11269.
--
wpt-commits: 939af265657f0fe6c59094cd9a519b6be9fdbac0
wpt-pr: 11294
--HG--
rename : testing/web-platform/tests/html/browsers/browsing-the-web/unloading-documents/unload/manual-001-1.html => testing/web-platform/tests/html/browsers/browsing-the-web/unloading-documents/unload/pagehide-manual-1.html
Automatic update from web-platform-testsSplit up WebCryptoAPI/derive_bits_keys/ with `variant`
Also use .any.js.
Fixes#11203.
--
wpt-commits: 864cba25d0ac3d2f49e851623370f565ca293cbe
wpt-pr: 11204
Automatic update from web-platform-testsNavigating to fragment scrolls with writing-mode: vertical-rl
This CL sets the alignment of the Anchor node in accordance, when
vertical-rl writing-mode is set
Bug: 844868
Change-Id: I8357bcccbc88ffcd3b5d01265737a5b60f1e59a8
Reviewed-on: https://chromium-review.googlesource.com/1075956
Commit-Queue: srirama chandra sekhar <srirama.m@samsung.com>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569214}
--
wpt-commits: 81918dc2da004801fba7f8833daf6930882831c3
wpt-pr: 11372
Automatic update from web-platform-testsDon't clear non-layout-object style for PseudoElements.
They are only used for storing an extra ComputedStyle for
display:contents pseudo elements as the ComputedStyle for rendering uses
a display:inline with only properties inherited for the parent element.
Bug: 854563
Change-Id: I4dd3d99b0dee0b538645d005b36347b469799244
Reviewed-on: https://chromium-review.googlesource.com/1107802
Reviewed-by: Anders Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569204}
--
wpt-commits: bcae036590041ef1704e2ba337e0577dac8c11c4
wpt-pr: 11594
Automatic update from web-platform-testsAdd a new test case for hit testing inline elements
This patch adds a new WPT that hit tests the empty region in an inline
element above a child with smaller font size (i.e., smaller height), and
expects to hit the inline element itself.
This helps us add related implementation in LayoutNG, since no existing
test case tests this behavior yet.
Bug: 851075
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: Ic538681530e17ea0d5fc49612376e30bdcf563d8
Reviewed-on: https://chromium-review.googlesource.com/1108560
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569082}
--
wpt-commits: cece9a142ba91d0e283a3206f272bde4876fe2a7
wpt-pr: 11596
MozReview-Commit-ID: CvzjoCi9YpJ
Automatic update from web-platform-testsAsync Cookies: Expose additional cookie attributes.
This CL exposes the following attributes in CookieListItem members
returned by cookieStore.get() and cookieStore.getAll(), and contained in
cookie change events.
* expires: "expiry-time" attribute
* domain: "domain" attribute, or null for host-only cookies
* path: "path" attribute
* secure: "secure-only-flag" attribute
The "same-site-flag" attribute will be exposed in a future CL that will
also add support for setting it.
The following attributes are not exposed intentionally.
* "creation-time", "last-access-time": no clear use case
* "persistent-flag": exposed implicitly as a null expiration time
* "host-only-flag": exposed implicitly as a null domain
* "http-only-flag": would always be false
This CL also fully implements setting a cookie's domain attribute, and
updates the relevant WPT tests.
CookieListItem is covered by the API explainer:
https://wicg.github.io/cookie-store/explainer.html
Cookie attributes are described in the cookie storage model:
https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-02#section-5.4
Bug: 729800
Change-Id: I8061f20d348b53ba8d0dabbd4b97564f6c3b4217
Reviewed-on: https://chromium-review.googlesource.com/1102339
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568972}
--
wpt-commits: 9392f67e3db464b3f5de73b900e125306a758221
wpt-pr: 11546