Automatic update from web-platform-testsCreating setAttribute in element.cc with arguments: USVStringOrTrustedURL
and ExceptionState
Changing attribute src of HTMLSourceElement and HTMLImageElement to URLString
Change of SetSrc of HTMLSourceElement and HTMLImageElement to hava arguments
USVStringOrTrustedURL; calling setAttribute mentioned above from it
Changing calls of SetSrc in other files so that the arguments match; wrapping
arguments and using ASSERT_NO_EXCEPTION
Adding tests for SetSrc
Bug: 739170
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ic99a338783bfcbfc5c2dca5061352367c2daeaec
Reviewed-on: https://chromium-review.googlesource.com/1137821
Commit-Queue: Orsolya Bernadett Batiz <orsibatiz@google.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575992}
--
wpt-commits: 085d47ef10ac636e73fe04e5c232046b329aa382
wpt-pr: 11997
Automatic update from web-platform-testsAdd more spec links to META.yml (#12045)
--
wpt-commits: f25bfad1f26616baa02da8d5f711e299194c5c98
wpt-pr: 12045
Automatic update from web-platform-testsReporting: Payload field should be `body`, not `report`
Per https://w3c.github.io/reporting/#try-delivery, the field in a
JavaScript report object that contains the body is called `body`, not
`report`.
Bug: 704259
Change-Id: Iba3186a0104c2192ced5e4233d55e042e05908f3
Reviewed-on: https://chromium-review.googlesource.com/1140193
Reviewed-by: Misha Efimov <mef@chromium.org>
Commit-Queue: Douglas Creager <dcreager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575894}
--
wpt-commits: eecf62171b50238462d3046818e108a2b98b655c
wpt-pr: 12030
Automatic update from web-platform-tests[Background Fetch] Support layout tests for the feature
An implementation of BackgroundFetchDelegate has been provided to
content shell which enables Background Fetches, without UI, to finish.
It uses the Download Service through a new dependency. This dependency
will be removed once the Download Service has been servicified, as
//content can depend on it directly from that point forward.
In context of the WPT tests, additional machinery has been added to
enable communication with the Service Worker, required for it to tell
the test about the result of the various Background Fetch events. The
"fetch.https.window.js" file now verifies the behaviour and results
of a single fetched file.
Bug: 864561
Change-Id: If53e6755ae8ea924712f5bdace4df4f658bc53d7
Reviewed-on: https://chromium-review.googlesource.com/1135536
Commit-Queue: Peter Beverloo <peter@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575919}
--
wpt-commits: bf11d1a166660d75383135e9d1610aa987857309
wpt-pr: 12043
Automatic update from web-platform-testsUpstream more IntersectionObserver tests to Web Platform Tests
This upstreams text-target.html, as well as a change to
client-rect.html. This also deletes the non-WPT copy of these
tests to avoid unnecessary test duplication.
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ic53b3be66ffa2b2dd5b77105eb2c8e02181bac81
Reviewed-on: https://chromium-review.googlesource.com/1136939
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Ali Juma <ajuma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575775}
--
wpt-commits: 69f77c2fe1ce1d8d6ac4ccd3f3261b56a573a73a
wpt-pr: 11984
Automatic update from web-platform-testsAdd test for document.open() in custom element constructor (#12037)
--
wpt-commits: 2468c3d48e432459fed53ae1d90bc176473cb94a
wpt-pr: 12037
Automatic update from web-platform-testsExpand coverage of performance-timeline IDL test (#12014)
--
wpt-commits: 0eead5e8bc6f214a59baa3096e061a96705f4d78
wpt-pr: 12014
Automatic update from web-platform-testsFix Create-on-worker-shutdown.any.js timing out when asserts fail
The worker's onmessage handled needs to be wrapped in a step_func()
Change-Id: Icfbad1936d9c9bd7fbd5522ce64f667f2699ef0d
Reviewed-on: https://chromium-review.googlesource.com/1139179
Commit-Queue: Nate Chapin <japhet@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575694}
--
wpt-commits: 5dc189dec91751495228e041055da8bc5bad943e
wpt-pr: 12015
Automatic update from web-platform-testsUse the empty string as the host when opening a socket to find an unused port (#11905)
This prevents some unfriendly error messages that can occure when the
user has not correctly configured their host file.
--
wpt-commits: b531f8af416b869192b99689b3aaa11d62906657
wpt-pr: 11905
Automatic update from web-platform-testsAdd missing </script> tag (#12020)
Fix#4183 as follows:
- Add missing </script> tag.
- Rename 002.manual.html as 002-manual.html, since manual test should use `-manual` suffix.
--
wpt-commits: 488c1a17c91b19c6f89104fa54ca5427dd40361d
wpt-pr: 12020
Automatic update from web-platform-tests[css-text] A leading white-space should break before handling overflow
Leading white-spaces are indeed breaking opportunities that should
prevent, if there are no other css properties forcing it, breaking text
in the middle of a word when honoring the word-wrap/overflow-wrap CSS
property.
We are doing so if the leading white-space sequence is longer than 1
character, but when we have a single leading white-space, we are missing
that breaking opportunity and we may lead to cases, like the one
described in the bug.
However, this breaking opportunity should be considered together
with other provided by the word-break CSS property (eg, break-word or
break-all).
There is a discussion [1] in the CSS WG github about this issue, which
provides an interoperability analysis of a few cases where a single
leading white-space character may produce different results, depending
on the browser and the combination of line-breaking properties.
[1] https://github.com/w3c/csswg-drafts/issues/2907
Bug: 854624
Change-Id: I49ec8282e899a32990662c104b48cab04057b909
Reviewed-on: https://chromium-review.googlesource.com/1130515
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575596}
--
wpt-commits: df5392444342a1c00422096a2febb9ceb0edf250
wpt-pr: 11877
Automatic update from web-platform-testsGardening: WPT: service-worker/fetch-event.https.html is slow.
The file has many tests. Give it a long timeout.
Bug: 863160
Change-Id: Idfad60c6e088b97bdc279c648037ecbf5d33861f
Reviewed-on: https://chromium-review.googlesource.com/1139935
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575594}
--
wpt-commits: dd380bb46b74d52022cf062620895cb862340c7d
wpt-pr: 12018
Automatic update from web-platform-testsCreated a flake8.ini file with flake8 configs. Using --append-config to tell flake8 to use this config file. (#11999)
--
wpt-commits: 75c5a8ab23083ae4f25ab7d8819ee54b5d232cc3
wpt-pr: 11999
Automatic update from web-platform-testsDon't extend selection for special elements on caret based deletes
We should not extend selection looking for special elements if the
delete operation has been triggered by a caret based selection.
This change is based on a recent [1] resolution of the Editing TF,
which acknowledges that behavior of single-cell tables must be the
same that multi-cell tables and even if the last character is
deleted, we should not delete the whole table structure.
A different case would be when the user actively selects the whole
content of a table; in this case, as we do in multi-cell tables,
the structure of single-cell tables should be deleted together
with the content.
[1] https://github.com/w3c/editing/issues/163
Bug: 731320
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I8c3e4efcc63410bf30b4889a715d92e9dda8189b
Reviewed-on: https://chromium-review.googlesource.com/1126255
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575591}
--
wpt-commits: d409e3882d9322655b6113d1e1688d657eec2b3d
wpt-pr: 11791
Automatic update from web-platform-testsMake longtask WPT layouttests less flaky
This CL improves tests in external/wpt/longtask-timing by:
* Increasing the length of a longtask from ~51 to ~60 to prevent a
coarse performance.now() granularity from affecting the tests.
* Wrapping the long tasks or iframes containing longtasks inside onload
handlers to ensure that the PerformanceObserver is registered by the
time the longtask is executed.
Test: third_party/blink/tools/run_web_tests external/wpt/longtask-timing
--iterations=1000 did not produce flakes.
Bug: 796668
Change-Id: Ic2ce59f7d221566f5443da9e9c7d36c7bd7bbe6f
Reviewed-on: https://chromium-review.googlesource.com/1138725
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575396}
--
wpt-commits: 930d2ef0ad1f16147953a4804abd808c89e244c9
wpt-pr: 12006
Automatic update from web-platform-tests[LayoutNG] Support rewinding unpositioned floats
This patch supports NGLineBreaker to rewind unpositioned
floats.
When rewinding floats occurs, LayoutNG either position them
incorrectly, or hit DCHECK in paint due to duplicated ID.
This patch fixes it for unpositioned foats by matching to
Edge and Gecko.
Blink considers such floats as if it were committed
(positioned in LayoutNG terminologies) and thus the position
is incorrect.
Bug: 636993
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: I884879b2034d2f63ae248f70de3edeb27d71cafe
Reviewed-on: https://chromium-review.googlesource.com/1136262
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575357}
--
wpt-commits: 53702f14ec8b654a9c1beb9a013cdc652703cb40
wpt-pr: 12000
MozReview-Commit-ID: 9ea37E6Spi2
Automatic update from web-platform-tests[WebXR] Use 'immersive' instead of 'exclusive'
The 'immersive' is more intuitive term than 'exclusive'[1].
[1] https://github.com/immersive-web/webxr/pull/371
Bug: 852524
Cq-Include-Trybots: luci.chromium.try :android_optional_gpu_tests_rel;luci.chromium.try :linux_optional_gpu_tests_rel;luci.chromium.try :linux_vr;luci.chromium.try :mac_optional_gpu_tests_rel;luci.chromium.try :win_optional_gpu_tests_rel
Change-Id: If5c5ab6563df40a783f9d346d319dceed1f7cc58
Reviewed-on: https://chromium-review.googlesource.com/1101601
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575344}
--
wpt-commits: 8da1b538cfd84d599d16f43be5a53007295e7a40
wpt-pr: 11541
MozReview-Commit-ID: L7fO5G7eHdv
Automatic update from web-platform-testswebdriver: add explicit call to session.end for delete session tests (#12004)
For the "delete session" command tests, the recent changes to the fixture
to create and delete sessions are bypassed. This means that at the end of
each delete session test, the harness thinks a valid session still exists.
Making an explicit call to `session.end()` at the end of each test will
put the tracking variables in the correct state for the harness to start a
new session with the next test.
--
wpt-commits: e385fa4925f71b4ac37de4c3ce235914748881f6
wpt-pr: 12004
Automatic update from web-platform-testswebdriver: remove expected focus event from file upload test (#12003)
The WebDriver specification states that only the "change" and "input"
events. We should not also be expecting the "focus" event.
--
wpt-commits: 2437f6f7405ddd2e7a76e666dc8a8dff9c83d17b
wpt-pr: 12003
Automatic update from web-platform-testsUpdating Safari executor to be able to execute wdspec tests (#11994)
Safaridriver also chokes on the selenium capabilities object, but replacing this with an empty capabilities object works.
--
wpt-commits: 1ef74288f808484bc12d1abbd49ac27d945296d1
wpt-pr: 11994
Automatic update from web-platform-testsChanging srcdoc from DOMString to HTMLString
A setter and a getter have been added to element.cc to support StringOrTrustedHTML
Bug: 739170
Change-Id: I2472d1920a08834e9bd4b1cb532f72f5305a699b
Reviewed-on: https://chromium-review.googlesource.com/1134994
Commit-Queue: Orsolya Bernadett Batiz <orsibatiz@google.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575240}
--
wpt-commits: 4b0008b5230f13161ecf5a4ab01905af857bacdd
wpt-pr: 11946
Automatic update from web-platform-testsUpdate the requestidlecallback IDL test (#9825)
--
wpt-commits: b1681c1d32cf1ca384b094dc9a7f2f7691a87f1c
wpt-pr: 9825