Automatic update from web-platform-tests
[Import Maps] Import tests
This CL imports post-#176 upstream reference implementation's tests
into wpt/import-maps/imported/, and
executes them under virtual/import-maps-without-builtin-modules/.
The pre-#176 existing tests are still left under
wpt/import-maps/builtin-support.tentative/imported/, which are excluded
by this CL from virtual/import-maps-without-builtin-modules.
To match with the expectation of post-#176 tests,
this CL modifies ImportMap::ToString() to output
strings (not single-element arrays) as right hand side.
https://github.com/WICG/import-maps/pull/176
Bug: 990561, 1010751
Change-Id: I652b35969d48e0147d07aa869ca3a97004f2f7a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842928
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706637}
--
wpt-commits: 2a907985ffc3ea3455fe277c584cadfe70b53623
wpt-pr: 19685
--HG--
rename : testing/web-platform/tests/import-maps/imported/resources/parsing-addresses.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/parsing-addresses.js
rename : testing/web-platform/tests/import-maps/imported/resources/parsing-schema.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/parsing-schema.js
rename : testing/web-platform/tests/import-maps/imported/resources/parsing-scope-keys.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/parsing-scope-keys.js
rename : testing/web-platform/tests/import-maps/imported/resources/parsing-specifier-keys.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/parsing-specifier-keys.js
rename : testing/web-platform/tests/import-maps/imported/resources/resolving-builtins.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/resolving-builtins.js
rename : testing/web-platform/tests/import-maps/imported/resources/resolving-not-yet-implemented.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/resolving-not-yet-implemented.js
rename : testing/web-platform/tests/import-maps/imported/resources/resolving-scopes.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/resolving-scopes.js
rename : testing/web-platform/tests/import-maps/imported/resources/resolving.js => testing/web-platform/tests/import-maps/builtin-support.tentative/imported/resources/resolving.js
Automatic update from web-platform-tests
[Import Maps] WPT: Do not check warnings
Because there are no ways to check console warnings from JavaScript.
Bug: 990561
Change-Id: I5f3827c4383e35c74521148aa2e3b912b52a5f13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1843507
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706592}
--
wpt-commits: e750d844555f6f178e505697da847f113f6f9a9a
wpt-pr: 19537
Automatic update from web-platform-tests
Portals: Add WPTs for navigations in portals
We test that methods for history manipulation work inside a portal
context and that their behaviour is the same as in a non-portal context.
We also test the new behaviour introduced with portals where a portal
and its host do not form a joint session history. So unlike iframes,
any session history change within a portal is done independently of its
host.
Bug: 914108
Change-Id: Ib1cdbe3e8d1c0e009eea1f05af28ef2971e8b353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1807773
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706587}
--
wpt-commits: f71a17b10a9d4c59e28a7095d59fdc4ef3428719
wpt-pr: 19333
Automatic update from web-platform-tests
Fetch Metadata: Add a test for `<embed>` navigated after loading.
@annevk noted in https://github.com/whatwg/fetch/pull/948#discussion_r331921654
that it was possible to navigate an `<embed>` after it loads. In this
case, it seems safest to ensure that this navigation shows up with a
destination of `embed` and a mode of `no-cors`.
That seems to be what we're sending today via Fetch Metadata, so let's
lock it in via this patch's tests. I suspect it's not what the
underlying `fetch()` API would show in a service worker, but we can
deal with that in a separate patch.
Bug: 1011763
Change-Id: I0156b2b1b467c914b15f6af50dfa37ce74db6c62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844996
Commit-Queue: Mike West <mkwst@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705518}
--
wpt-commits: 5afa7f6c3321e6435f6e4e119214f7c826dd8bae
wpt-pr: 19546
Automatic update from web-platform-tests
[pointerevents] Stabilize test
Previously, this test conditionally declared a subtest, making it
difficult to compare results between browsers. Depending on the
implementation status, the results could be interpreted in a number of
ways:
- a failing single-page test
- a timed out single-page test
- a completed test with a single failing subtest
- a completed test with a single passing subtest
Refactor to explicitly opt-in to the single-page test feature and to
consistently report unexpected behavior via unhandled Promise rejections
and uncaught exceptions.
--
wpt-commits: 3b1798ba2792fd0d9eabb88c9e41d8240153c219
wpt-pr: 19708
Automatic update from web-platform-tests
Revert "Composited Worklet Animations: Fixed updating local time on main thread."
This reverts commit 1901912de23a31a49cae70f246aaf86dfb0923c2.
Reason for revert: potential cause for flaky tests. Please see bug.
Bug: 1014966
Original change's description:
> Composited Worklet Animations: Fixed updating local time on main thread.
>
> This CL changes how local time of composited worklet animations is updated on main thread:
> instead of polling local time on main thread, the local time is posted via animation events
> by the composited thread to the main thread.
>
> Design document: https://docs.google.com/document/d/1vUxaKBLDHQv9ACJUQJH4RXjuQTlWIsSiAFYkMrjccyc/edit?usp=sharing
>
> Changes made:
> - Expanded AnimationEvent to support worklet animation time update event type.
> - Reused existing mechanism of posting animation events to the main thread to support new
> event type.
> - Removed "peek" logic.
> - Enabled tests that previously failed.
>
>
> Bug: 943787
> Change-Id: I2d285506739ea623e292927d21e54910fb7e24bd
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826872
> Reviewed-by: Majid Valipour <majidvp@chromium.org>
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
> Cr-Commit-Position: refs/heads/master@{#706078}
TBR=flackr@chromium.org,majidvp@chromium.org,gerchiko@microsoft.com
Change-Id: Ic5bfd6532578276fe9e0de80f96f343a863e4f0f
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 943787
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865350
Reviewed-by: Parastoo Geranmayeh <parastoog@google.com>
Commit-Queue: Parastoo Geranmayeh <parastoog@google.com>
Cr-Commit-Position: refs/heads/master@{#706497}
--
wpt-commits: 315d2d420f1127b933d396691211bdaa08874976
wpt-pr: 19733
Automatic update from web-platform-tests
Add rev-list wpt subcommad (#19536)
Adds the rev-list subcommand for the wpt tool which is basically a
wrapper for the `git for-each-ref` command filter for `merge_pr_*` tags.
The `wpt rev-list` will show the more recent revision closer to each
epoch step for the epoch size defined in the command line.
This command is executed for a specific timestamp which is (now -
threshold). This threshold is set to 600 seconds.
Iterates the tagged revisions in descending order finding the more
recent commit still older than a "cutoff_date" value.
When a commit is found "cutoff_date" is set to a new value multiplier of
"epoch" but still below of the date of the current commit found.
This is needed to deal with intervals where no candidates were found
for the current "epoch" and the next candidate found is yet below
the lower values of the interval (it is the case of J and I for the
interval between Wed and Tue, in the example). The algorithm fix
the next "cutoff_date" value based on the date value of the current one
skipping the intermediate values.
The loop ends once we reached the required number of revisions to return
or the are no more tagged revisions.
Fri Sat Sun Mon Tue Wed Thu Fri Sat
| | | | | | | | |
-A---B-C---DEF---G---H--IJ----------K-----L-M----N--O--
^
now
Expected result: N,M,K,J,H,G,F,C,A
--
wpt-commits: 51263e8aaf6d67f36ffd40b34563efcf2015b453
wpt-pr: 19536
Automatic update from web-platform-tests
Fixup a css-shapes test broken by #19577 (#19731)
--
wpt-commits: 88c0d6780f897eacd4783e1aaf0ff15756515530
wpt-pr: 19731
Automatic update from web-platform-tests
[storage-access-api] rename idl.window.js to idlharness.window.js (#19728)
To make it easier to search for idlharness.js tests on wpt.fyi.
--
wpt-commits: 9263aa90326be2822b1bea9bae74935dd74371f3
wpt-pr: 19728
--HG--
rename : testing/web-platform/tests/storage-access-api/idl.window.js => testing/web-platform/tests/storage-access-api/idlharness.window.js
Automatic update from web-platform-tests
Retry the download of the webkitgtk nightly built product. (#19725)
* It has been observed that the download on taskcluster fails with
a "socket.error: [Errno 104] Connection reset by peer" error.
* This moves the download code to a new function that will retry
the download in that case. Up to 3 times by default.
--
wpt-commits: 0541c232203b8d4a9b229791e5ef12ea0f9836d3
wpt-pr: 19725
Automatic update from web-platform-tests
taskcluster: raise testharness chunks to 16 (#19724)
* Some testharness runs are timing out on the daily runs of webkitgtk.
* Before trying to raise the timeout, try to raise the number of chunks.
--
wpt-commits: ac16b468317c4d51f31060d139679e1a00e302c7
wpt-pr: 19724
Automatic update from web-platform-tests
Reduce number of reftest chunks for master runs
Reduce number of reftest chunks to 5 to save some resources; these
never limit overall e2e time.
--
wpt-commits: a536bc234b54a8062e4cfa01c05becbc49cdea52
wpt-pr: 19682
Automatic update from web-platform-tests
Remove @lukebjerring as interfaces/ reviewer 🙁 (#19722)
This way, all @autofoolip PRs in interfaces/ go to @foolip.
Drive-by: clean up admin docs. kereliuk@google.com also bounces.
--
wpt-commits: bd5ca81029315b5715d782e87861820d7a154400
wpt-pr: 19722
Automatic update from web-platform-tests
[WebNFC] Don't restrict arrayBuffer() to json and opaque records (#19720)
--
wpt-commits: f0607e0ceb2d7b44c60772458d22323bd796621a
wpt-pr: 19720
Automatic update from web-platform-tests
[WebNFC] Add test for focused iframe
Following Web NFC spec change at https://github.com/w3c/web-nfc/pull/383,
this CL adds a test to check NFC scanning from top-level document will
not be stopped when an iframe is focused
Bug: 996250, 520391
Change-Id: If89079d7bf9d7dc58587abcd0c9a9a797420aa50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862475
Reviewed-by: François Beaufort <beaufort.francois@gmail.com>
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Cr-Commit-Position: refs/heads/master@{#706321}
--
wpt-commits: 7124815437c81fa178482f752abd28817bae97ea
wpt-pr: 19689
Automatic update from web-platform-tests
Stop using private properties for data properties of cross-origin properties
Since Blink properly supports the incumbent realm now, there is no more need to use OriginSafeMethodSetter, which sets value via V8PrivateProperty.
So there is no need to use V8PrivateProperty also in OriginSafeMethodGetter.
This CL makes it possible to handle "data properties" of cross-origin properties as the proper data properties.
Bug: 715418
Change-Id: I336a8459b80bc63d08a248f3ed7a34dc0806e5ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844520
Commit-Queue: Marina Sakai <marinasakai@google.com>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706304}
--
wpt-commits: ca9c14143725ef54ffa4d0b8da46b6488d772649
wpt-pr: 19589
Automatic update from web-platform-tests
Fix spec links to use actual anchors that exists
--
wpt-commits: 0e1bcae7f14564f0946484c9e8021b0a6fdcb68d
wpt-pr: 19718
Automatic update from web-platform-tests
[CSS] Add test to to ensure that ::part overrides inline-style.
This test is already passing for blink but some other browsers fail.
This test is a clone of simple.html but moves the color inline.
Bug: 1014400
Change-Id: I4810222d43f99ae229afa58458e1830202b7d444
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862134
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706285}
--
wpt-commits: 8f14d88acb82bedaaa4bfacd7e9b6d262e21cdc2
wpt-pr: 19702
Automatic update from web-platform-tests
Add exception handling to css build script when parsing test metadata
--
wpt-commits: afeb195d4ea449f23e34e0a3352d8a392a430ef1
wpt-pr: 19717
Automatic update from web-platform-tests
add meta charset due to utf8 in author name
--
wpt-commits: 045e538ea576a34bb9e66afcc782199740813434
wpt-pr: 19716
Automatic update from web-platform-tests
NG/ContentSize: Save unconstrained intrinsic block size in NG for overflow calc.
This patch saves the unconstrained intrinsic box size during the
block layout algorithm in order to use it for overflow calculation
in the node. Since we can override the intrinsic size with css-content-size,
we may cause scrollbars to appear. By using unconstrained size, we retain
correct behavior in which scrollbars only depend on the child content,
and not on content-size override.
R=chrishtr@chromium.org, ikilpatrick@chromium.org
Bug: 991096
Change-Id: I0d9cb270ee710b759f93202497f69bf72544f81a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833074
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706135}
--
wpt-commits: 50fa6ade9bda8c138ee37878c8442f33af09cb7d
wpt-pr: 19642
Automatic update from web-platform-tests
Fix how CORB async_test(s) work.
Some CORB tests run in parallel, because they use `async_test`. See
https://web-platform-tests.org/writing-tests/testharness-api.html#asynchronous-tests:
"Keep in mind that other tests could start executing before an
Asynchronous Test is finished."
This CL fixes such tests, to make sure that they either migrate to
`promise_test` [1] or avoid using shared/global state.
[1] https://web-platform-tests.org/writing-tests/testharness-api.html#promise-tests
says "Unlike Asynchronous Tests, Promise Tests don’t start running until
after the previous Promise Test finishes. Under rare circumstances, the
next test may begin to execute before the returned promise has settled.
Use add_cleanup to register any necessary cleanup actions such as
resetting global state that need to happen consistently before the next
test starts."
Bug: 1011410
Change-Id: Ib369e6cd07aed2daaf6347ae5d6f777a2c0835db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841898
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706131}
--
wpt-commits: 2bd57e011c95fb1877361bb2166563174409b63d
wpt-pr: 19552
Automatic update from web-platform-tests
[LayoutNG] Fix hit-testing image list markers
This patch fixes hit-testing image list markers. The previous
fix for hit-testing list markers (r682470 crrev.com/c/1726571)
didn't cover image list markers, and unfortunately the test
did not cover the case.
Bug: 1002417
Change-Id: Ieefcfa91240570a3d59265cf7e75c802396da6d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862873
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706094}
--
wpt-commits: 01fc47690771e6e7df8c3778b8c1d35e7bfde284
wpt-pr: 19705
Automatic update from web-platform-tests
Use the "scaled" font when computing baselines for SVG text
The font code (FontMetrics::AscentDescentWithHacks specifically) will
(may) mangle (round) the ascent and descent, meaning that for small
font-sizes all precision is lost.
Using our (potentially) "rescaled" Font for computing the baseline for
text gives us a chance to recover some of the precision lost in the
rounding process.
Bug: 1013859
Change-Id: Ieaadaf558315b8a082331ac76deeb52bcf3b11c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859961
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#706091}
--
wpt-commits: 9a5320a1736375a883f68f3bc74fe5d05a657624
wpt-pr: 19707
Automatic update from web-platform-tests
Composited Worklet Animations: Fixed updating local time on main thread.
This CL changes how local time of composited worklet animations is updated on main thread:
instead of polling local time on main thread, the local time is posted via animation events
by the composited thread to the main thread.
Design document: https://docs.google.com/document/d/1vUxaKBLDHQv9ACJUQJH4RXjuQTlWIsSiAFYkMrjccyc/edit?usp=sharing
Changes made:
- Expanded AnimationEvent to support worklet animation time update event type.
- Reused existing mechanism of posting animation events to the main thread to support new
event type.
- Removed "peek" logic.
- Enabled tests that previously failed.
Bug: 943787
Change-Id: I2d285506739ea623e292927d21e54910fb7e24bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826872
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#706078}
--
wpt-commits: 3eecf8c3962bb5217d813922f5c1b286cddf3568
wpt-pr: 19345
Automatic update from web-platform-tests
Port IndexedDB Blob Web Tests to web-platform-tests.
This CL ports the Blob related IndexedDB Web Tests to WPT tests.
Bug: 866164
Change-Id: Ie2b1b6ddc0c1ddbbb92478a2d5c81bd669c30e45
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1807963
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Sertay Sener <sesener@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#704755}
--
Set long timeout for IndexedDB/blob-contenttype.any.js
--
wpt-commits: cb93440dc5c898d6e3faac411464c90c670c2f22, 72f59efdbd1bb49bd6f5b2f3366ed595c6783c39
wpt-pr: 19102
Automatic update from web-platform-tests
Do not invalidate container for outlines
This patch reverts https://crrev.com/563452 which is causing crashes
due to not marking the paint layer as needing repaint (see new
testcase). The inline outline painting code was re-designed in
https://crrev.com/591748 to not paint from the container, so this
invalidation codepath is no longer needed. The original test for
https://crrev.com/563452 is no longer crashing.
Bug: 1011699
Change-Id: I42af2ffd3a5a3425fc2acaf0771a992f09adde57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859831
Auto-Submit: Philip Rogers <pdr@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705968}
--
wpt-commits: 47f50fdf187474e184bafebbea8ce16736c3b22f
wpt-pr: 19699
Automatic update from web-platform-tests
Fetch Metadata: split up `document` destination.
As discussed in
https://github.com/w3c/webappsec-fetch-metadata/issues/45,
We have decided to shift the model around nested navigations from
exposure via the request's `mode` to its `destination`. This patch
splits the existing `document` destination into three parts:
- `document` for top-level navigations and, for the moment, <portals>.
- `iframe` for <iframe> navigations.
- `frame` for <frame> navigations.
Subsequent patch will remove the `nested-document` mode when we're ready
to ship `Sec-Fetch-Dest`.
Bug: 1011724
Change-Id: I23f23922fb49523aa050f59cbf13aabc086600bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847295
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Yifan Luo <lyf@google.com>
Cr-Commit-Position: refs/heads/master@{#705527}
--
wpt-commits: 9fffe2189f5c87287393486e1f1e260cf71dcddf
wpt-pr: 19704
Automatic update from web-platform-tests
Fetch Metadata: Split `sec-fetch-dest` out from other headers' tests.
Bug: 1012190
Change-Id: Id5029e303d1fc5e171f8efdd2946ffe5eeef52bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844823
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Yifan Luo <lyf@google.com>
Cr-Commit-Position: refs/heads/master@{#703642}
--
wpt-commits: e6ca5a0decb3db94d808eeb7c0c0688196b0bbd1
wpt-pr: 19550
Automatic update from web-platform-tests
[css-writing-modes] Fix bug in wm-propagation-001
Text content must be directly inline in the html element to observe its
writing mode's used value. If placed in a descendant pseudo, it will
inherit from the computed value instead.
--
wpt-commits: ae14a216a78d3585dea107d1ce73f784c7448072
wpt-pr: 19698
Automatic update from web-platform-tests
webdriver: fix test_spin_event_loop (#19585)
Fixing an element_click test by scheduling the delayed function to
execute right away.
--
wpt-commits: 4b9b91843ea06b85b53b5e0c027f9b76cdc8fd85
wpt-pr: 19585
Automatic update from web-platform-tests
HTML: do not test IDL specifics in iframe load event test (#19691)
--
wpt-commits: 858fa42be06f4f4281f4b3f0c48e0f33b5676e89
wpt-pr: 19691
Automatic update from web-platform-tests
Add tests for NFC API in non-visible document (#19664)
--
wpt-commits: 9f31d497bf87bdf5ebc3ba70b5cb9f87786f4071
wpt-pr: 19664
Automatic update from web-platform-tests
Test that MediaQueryListener calls EventListener::handleEvent
--
wpt-commits: 74286c98a9f403921e3d90af5b8693b437733ff8
wpt-pr: 18390
Automatic update from web-platform-tests
[LayoutNG] Allow negative margins to stay on the line after overflow
This patch allows atomic inlines to stay on the line even
when it appears after the line overflowed, if its negative
margins can bring the position back to inside of the line.
This is not a well-defined behavior in the CSS spec, but
legacy/WebKit/Gecko do this at some levels, though not really
interoperable.
Bug: 1001000
Change-Id: If8cfc5d51de14c8de6a9caa78fa10abaf6f1b5b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859424
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705848}
--
wpt-commits: eb78a40aac4a0072fd12585c7f29efde938a2e33
wpt-pr: 19687
Automatic update from web-platform-tests
[LayoutNG] Fix NGLineBreaker not to hang on negative margins
This patch fixes a case where |NGLineBreaker| loops
infinitely when there is a negative margin. The case was a
regression by r701601 (crrev.com/c/1826063).
Handling combinations of a) trailable items, b) empty spans,
and c) negative margins together is becoming more complex as
we fix issues. This patch revises how we handle them.
One of the complexities is open tags being ambiguous; e.g.,
this open tag is not trailable and thus breaks before it:
<span>text
but these open tags are trailable:
<span> text
<span></span>text
<span> </span>text
and it can even nest more, contain floating/out-of-flow
objects, or have negative margins.
Before this patch, |NGLineBreaker| tries to stop as early as
possible, rewind, and consume trailable items. The last part
(consuming trailable items) is scarly because rewind loops
can occur if we try to rewind again.
The new approach is to try to consume possibly trailable
items before it rewinds, and avoids consuming after rewind.
There might be cases where the new approach consumes more,
but `blink_perf.layout` is neutral:
https://pinpoint-dot-chromeperf.appspot.com/job/11fdf216c20000
In the test, case 2 and 5 fail in legacy, because the legacy
behavior is based on a bug (crbug.com/979894) or the new
behavior makes more sense, and the new behavior is
interoperable with Edge/Gecko.
Note, this change should be able to eliminate |kTrailable|
state, and that eliminate consuming after rewind completely,
but we still need it in a few places. It is for future
patches to clean them up.
Bug: 1011816
Change-Id: Ic915a26f1ee570ebe999ffbeee680659dcbd9789
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849737
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705844}
--
wpt-commits: d36a8bac6d6d0c14fa6d7475b6f06ffd26967b25
wpt-pr: 19660
Automatic update from web-platform-tests
The block-offset of a spanner may affect layout.
We already had code that copied to the block-offset from the spanner
placeholder to the actual spanner layout object, but we also need to
make sure that it actually gets laid out.
See test: In the initial layout pass we'd set the block-size of the
first column row (with the empty DIV) to the block-size of the multicol
container. Then we'd bump into the spanner, and realize that this
block-size wouldn't do, since we need to balance columns in front of a
spanner. Because of this initial block-size of the column row, the
initial layout pass of the spanner would put the spanner below that,
tricking the machinery into believing that we need a break inside the
spanner. In the next layout pass the block-size of the column row would
be corrected, and also the position of the spanner. But we wouldn't
re-lay out, and thus incorrectly keeping a pagination strut in the
middle of the spanner.
Bug: 1006249
Change-Id: If7ec10389ba5f6e78d9ecb5fd4ad7fd113c128bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859977
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705646}
--
wpt-commits: 20a55f606de85d95a46cd19b423c9215cb39898c
wpt-pr: 19677
Automatic update from web-platform-tests
wake lock: Implement new proposed API.
This is another big update to the implementation, which now follows the
API proposed in https://github.com/w3c/wake-lock/issues/226.
From a Blink/Chromium internals perspective, things have not changed much,
and we still perform the same permission checks and connect to the wake lock
service via WakeLockStateRecord. The biggest change is that WakeLockController
was merged into WakeLock itself.
From an end-user perspective, though, the API now looks like a mix of the
old, navigator-based API and the one we implemented a few months ago:
* The main idea is that WakeLock.request() no longer returns a promise that
does not resolve while the lock is held, as that is not very intuitive.
Instead, it returns a new WakeLockSentinel object.
* WakeLockSentinel is a new interface that can release() a lock and receive
"release" events.
* We do go back to a Navigator-based API, but we also support
WorkerNavigator.
* There is no WakeLockRequest interface or state tracking in the WakeLock
interface.
* WakeLock.requestPermission() was removed.
* Consequently, we now have a WakeLockEvent interface.
The changes to the spec still need to land, but there is some rough
consensus on what the API should look like, and we do not want to miss the
M79 branch cut.
Bug: 257511, 1010162
Change-Id: If1baed914ccd9eb7103a1bb71a40529976777ec2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849683
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#705632}
--
wpt-commits: 1a69ff8bc7a40d2e37ce0ce822e980a94bad9333
wpt-pr: 19600
Automatic update from web-platform-tests
Rewrite wpt/svg/animations/slider-switch.html to use 'begin' as trigger
The interval timer could end up racing with the animation update timer,
meaning that the new animation values had not yet been applied when
the |retries| counter reached zero and the assertions were made.
Refactor the test to trigger the next "action" (new pair of clicks or
checking the result) when one of the timed elements listening on the
"b.click" event has begun. Also change |retries| into counting how many
clicks are remaining (rather than how many interval timer firings).
Bug: 1013736
Change-Id: I374cb9c499ca18a791f76dabcb1db8bcd6f38461
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859955
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#705574}
--
wpt-commits: c7abd94317e9a039ee0a93324571e94b91a9ab09
wpt-pr: 19672
Automatic update from web-platform-tests
Test empty script elements (#19676)
* Test empty script elements
--
wpt-commits: b9b9fb904eff219906f7f9a5742c8215d5e65ec8
wpt-pr: 19676
Automatic update from web-platform-tests
[docs] Document wptrunner classes
These classes are referenced from the ReStructuredText-formatted
documentation.
--
[docs] Fix build process for wptrunner
The Mozilla-provided "intersphinx" metadata does not include an entry
for the "mozlog" module. Replace the rST cross-referencing roles with a
hyperlink to the documentation webpage.
--
[docs] Integrate wptrunner documentation
--
[docs] Remove wptrunner-specific tooling
--
[docs] Remove outdated content
--
[docs] Consolidate info on expectations files
--
[docs] Expose a single index for wptrunner docs
--
wpt-commits: 61adf1dd0f37b016ce851722c2f3045560c899e1, 1a6f43365b8230df3b25ed28627802199e618b30, 355db3e8653970fab13c78fee743eee667be6025, f5c837e32ff3961266ba76febda0e9b9f520a28e, 94a9a8f0d9520932ffbda2ad6ff7dfcab144979f, 197f2cf0b343f17dc3f0d85b33cdcc62039d9421, 6ffed675082f1faae9b1ca16908efbb333c43dbd
wpt-pr: 19647
Automatic update from web-platform-tests
Regenerate pregenerated certs
We've needed to do this since 2cccd822f95, but haven't. Whoops.
This also stops outputting the text form of the certificate before the
PEM header as macOS/iOS's Security.framework only scans the first 8192
characters for the beginning of the header.
--
Readd documentation on how to generate pregenerated certs
This accidentally got removed in afd4200510.
--
wpt-commits: 49d6007b38f818f208f672f106f2388db7ff10d8, b88d541c8cc7868ad6b9eefab4949602d826afbe
wpt-pr: 19626
Automatic update from web-platform-tests
Switch WebKitGTK testing to Ubuntu (harmonize docker based testing) (#19595)
Previously a Dockerfile based on Debian was added for WebKitGTK testing
with the idea of reusing the built products that build.webkit.org is
producing.
That was done with the idea of having dozens of new nightly builds available
at a day, which doesn't seem to match the needs for WPT testing/runs.
It seems that having one new nightly a day (or even two a week) is more
than enough. At that rate is more than reasonable to do new builds for
testing with Ubuntu 18.04.
And it seems that harmonizing the testing of the Linux based browsers on
the same docker image has several benefits, including making easier future
maintenance.
This switchs the WebKitGTK testing to using Ubuntu 18.04.
--
Add a nightly channel for testing with WebKitGTK on taskcluster. (#19595)
The nighly channel downloads the last nightly tarball available at
https://webkitgtk.org/built-products and installs it on taskcluster
when the test start.
This tarball is generated using the webkitgtk internal JHBuild, that
builds several third-party libraries needed for webkitgtk layout tests
and then builds webkitgtk on top of this libraries. Because of this
using this tarball requires installing quite a lot of extra dependencies
(that are needed by this extra third-party libraries). A script is
included inside the tarball to install this dependencies.
--
wpt-commits: 0caf257227379666f62c717d1b3ac2319659d315, 60d0c91c095561dea605458044b55f52a8f14b79
wpt-pr: 19595
Automatic update from web-platform-tests
add test for CSS grid align-content property (#19665)
* add test for CSS grid align-content property
--
wpt-commits: a9000138e7b5cee7caceb58f5930ccc41afe2253
wpt-pr: 19665
Automatic update from web-platform-tests
[GitHub Actions] run manifest_build.py directly on Ubuntu 18.04
Fixes https://github.com/web-platform-tests/wpt/issues/19380.
Running faster increases the risk that the GitHub search API can't
find the pull request yet, so add retry.py with a --delay value that
with 5 iterations adds up to a total of 15 minutes waiting.
--
wpt-commits: 2277f7c78c82bac89dc4e5ad9e710c9fc8d4c662
wpt-pr: 19580
Automatic update from web-platform-tests
Fix call of SafeConfigParser.get for compatibility with Python3
--
wptcommandline: use iterkeys, itervalues and iteritems from six
This is done in order to improve compatibility with Python3
--
manifestupdate: use iterkeys, itervalues and iteritems from six
This is done in order to improve compatibility with Python3
--
wpt-commits: 04af25d084bdd08cf8876d406a2648ba75135e53, 67e0efed8cb629ca03a9be3857094d2723ba41c9, ef7efacd47c6562946a32bb73d8ac5649cebacf9
wpt-pr: 19654
Automatic update from web-platform-tests
[Azure Pipelines] trigger CI builds only on certain branches (#19668)
The CI builds do nothing for most branches and create a lot of no-op
builds in the Azure DevOps UI, making it harder to find the real ones.
PR builds are not affected by this.
--
wpt-commits: 6cc386397534f2fb2235b5638fa3d8e616faab29
wpt-pr: 19668
Automatic update from web-platform-tests
[sensors] Round off Ambient Light Sensor readouts to the nearest 50 Lux.
There have been some concerns regarding the precision of readouts from the
Ambient Light Sensor. To decrease the entropy, we are rounding off the
illuminance value to the nearest 50 Lux to mitigate the known attack
vectors as summarized in [1].
[1] https://github.com/w3c/ambient-light/issues/13#issuecomment-302393458
This CL is based on
https://chromium-review.googlesource.com/c/chromium/src/+/1695412 by
Rijubrata Bhaumik and myself.
Bug: 642731, 606766
Change-Id: I85449bdb835e8486b080fc269938b6c96f000c2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834346
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#705486}
--
wpt-commits: b5c2b81b664dbf9fccf7316017ada0878fc10fa1
wpt-pr: 19467
Automatic update from web-platform-tests
[LayoutNG] Use legacy borders when painting table cell fragments
NG fragments don't support collapsed borders yet. This manifested with
background-clip. When the position/size of the clipped background was
determined, the cells' full borders were used, not half of the winning
border as is correct in collapsed mode.
Bug: 1008400
Change-Id: I53a80c88d854136e8d3f540fe7b8c969152aad13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1858519
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705454}
--
wpt-commits: 8ecb8a727ddcfc2f5d0c2a996186a19654cae6f6
wpt-pr: 19658
Automatic update from web-platform-tests
[html] Clean state between dialog positioning tests
Calling `reset()` at the end of every test to close the modal dialog
will only be invoked if the test passes. If an expectation fails, the
call to `reset()` will never run and the dialog will remain modally open
on the page. This causes all further tests to fail because calling
`showModal()` on the dialog while it is open is an error.
Instead, set up `reset()` to be called as a cleanup after every test
regardless of whether the test passes or fails.
--
[html] Fix closing dialogs in showModal test
The `add_cleanup()` calls need to be registered outside of the
`assert_throws` block to ensure that the dialogs are actually closed.
--
wpt-commits: e27c96ebb41237468c9306e629756a2459982dbd, 79c38259f4deb0d7967a1ed8419185909120fd9b
wpt-pr: 19657
Automatic update from web-platform-tests
Discard current interval if 'end' attribute change renders it invalid
If a mutation of the 'end' attribute ended up introducing an offset
value that was before or at the begin time for the current interval,
we'll no longer have a valid interval (unresolved active duration).
In this case do what ResolveInterval() does and discard the current
interval.
Bug: 1013365
Change-Id: I871c2c235f179dabb31c2347c47f83c53d44b1d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855963
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#705397}
--
wpt-commits: 52024c8e73e274dff4f02bf50b5490a80ed2a52e
wpt-pr: 19641
Automatic update from web-platform-tests
[css-grid] Accommodate spanning items crossing flexible tracks
The specification added a step to increase sizes to accommodate spanning
items crossing flexible tracks instead of ignoring their contents
completely. This is done after handling all grid items that don't cross
such tracks, and this time items are considered together, not grouped by
their span size.
Spec: https://drafts.csswg.org/css-grid/#algo-spanning-flex-items
BUG=935102
TEST=third_party/blink/web_tests/external/wpt/css/css-grid/layout-algorithm/grid-flex-track-intrinsic-sizes-001.html
TEST=third_party/blink/web_tests/external/wpt/css/css-grid/layout-algorithm/grid-flex-track-intrinsic-sizes-002.html
TEST=third_party/blink/web_tests/fast/css-grid-layout/flex-and-content-sized-resolution-columns.html
TEST=third_party/blink/web_tests/fast/css-grid-layout/grid-gutters-and-flex-content.html
Change-Id: Ic91a2eb471fae23cde1570c461f491cd5335d771
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1492337
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Sergio Villar <svillar@igalia.com>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#705228}
--
wpt-commits: 8473169330be3b6594cc47f035d3a2c204fd4666
wpt-pr: 19373
Automatic update from web-platform-tests
Propagate writing-mode and direction from body to html.
Direction and writing-mode is propagated from body to the viewport, but
when the computed value of those properties are different between the
root and body elements, their used values are the computed values of the
body element. The computed values are not affected by this.
We implement this propagation by using a ComputedStyle on the
HTMLHtmlElement's LayoutObject which has the propagated values for
direction and writing-mode.
The modified tests relied on direction on #container being different
from the #container parent. That is no longer possible with body being
container and the used direction value of body propagated to html.
The tests were modified to use a child of body as container instead,
the removed 8px margin was just replicating the body margin and we do
not want that on the #container div.
Spec: https://drafts.csswg.org/css-writing-modes-3/#principal-flow
TEST=external/wpt/css/css-writing-modes/wm-propagation-002.html
TEST=external/wpt/css/css-writing-modes/wm-propagation-body-033.html
TEST=external/wpt/css/css-writing-modes/wm-propagation-body-037.html
Bug: 988585
Change-Id: I2879c8fdc082940d2baaf67e126b28915f9f1eca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852786
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705218}
--
wpt-commits: c9ddd877ad6714aabd1509438a8648ed62e38035
wpt-pr: 19637
Automatic update from web-platform-tests
Change text directive to text=
Change the targetText= directive to text=. Also remove the
non-fragment-directive case and the ## delimiter since we definitely
won't be using them.
Updated all tests to use :~:text= syntax.
Updated web platform tests to reflect text= change and delimiter change
to :~:. Tested updated WPT locally with
run_web_tests.py --additional-driver-flag=
'--enable-blink-features=TextFragmentIdentifiers'
Bug: 1008874,1007016
Change-Id: Ic7f3db39e0a17d5adb8186b2ab5081d60553bd8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1835892
Commit-Queue: Nick Burris <nburris@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703317}
--
wpt-commits: 12b4f7d9775a9de8307230fc2e247412529f6c62
wpt-pr: 19527
Automatic update from web-platform-tests
Update scroll to text feature detectability API
Update the feature detectability API to
window.location.fragmentDirective per
https://github.com/WICG/ScrollToTextFragment/issues/19
Also updated web platform tests and confirmed tests pass.
Bug: 1000308
Change-Id: Ib2391abe3d142d57cea61840e721ed35c81089af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850364
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#705010}
--
wpt-commits: 084d7fc3c77c1c5d581395fa834245ed527b0664
wpt-pr: 19610
Automatic update from web-platform-tests
Clear the current interval when no more intervals can be resolved
When no more intervals can be resolved, ResolveInterval(...) will return
an interval that return false from IsResolved() (meaning it has no
finite begin time). When this happens we should "clear" |interval_| by
setting it to an unresolved interval.
This fixes the behavior of SVGAnimationElement.getStartTime() which now
correctly report (throws) when the last interval of element has ended.
Add a new test for that and move an old somewhat related test to WPT.
Also adjust SVGAnimationTestCase.js which uses this to offset the sample
times (although in most cases) to avoid the debug dump when there's no
current interval (no tests actually rely on the old broken behavior).
This makes us match Firefox.
Bug: 998526
Change-Id: Idcf348343768ffc9392e29af2e976b9a3a1e31aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849897
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#705019}
--
wpt-commits: 052b945a3500b6e4c975f87ab2ad62931df1aac0
wpt-pr: 19619
Automatic update from web-platform-tests
[docs] Simplify README
Prior to this patch, the documentation for the "resources" directory was
incomplete and included a reference to external content which was
duplicative of existing instructions.
Reduce the contents of the "resources" documentation to minimally
describe the directory and direct readers to the canonical information
sources.
--
wpt-commits: 6980a1163b7c2fca04e3162a8492ebe71bea785a
wpt-pr: 18970
Automatic update from web-platform-tests
Fixed all browser's use of is_alive property
Various Browser.is_alive() functions were referencing the
WebDriverServer.is_alive property, but calling it as if it were a
function. Encountered this when running `wpt run --debugger ...`
--
wpt-commits: 8be26a07bc6cc42e781a34da1d434b02ac3536f9
wpt-pr: 19166
Automatic update from web-platform-tests
Update marionette_driver from 2.8.0 to 3.0.0
--
wpt-commits: e3990b27df9cbc30a1dc4c3877914f164aeb0052
wpt-pr: 19625
Automatic update from web-platform-tests
Update mypy-extensions from 0.4.1 to 0.4.2
--
wpt-commits: f9c9d79390a64bc16ae43ee3ab7e4c91c42b4c00
wpt-pr: 19499
Automatic update from web-platform-tests
Don't depend on execfile in virtualenv.py
This is gone in Python 3 and prevents otherwise Py3-compatible wpt
commands working with `python3 wpt`.
--
wpt-commits: ccbf1f9f3e36db12e86de39160317bce0b4fa38f
wpt-pr: 19445
Automatic update from web-platform-tests
Passing Android device serial to chromedriver.
The Android device serial number, specified by the --device-serial
command-line option, was never passed to the chromedriver server.
This resulted in chromedriver always using the first device or
emulator.
Bug: None
Change-Id: I1a4cb1c45739f24da5ea0f6cfb3726c84ff68fa1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848264
Commit-Queue: Chris Mumford <cmumford@google.com>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704795}
--
wpt-commits: f68f786b7dd842cec9ccd0128a3397d875d53cef
wpt-pr: 19582
Automatic update from web-platform-tests
Move portals web tests into WPT
There's nothing in these tests that is blink specific, so we make them
web platform tests.
Bug: None
Change-Id: I88a17bcfa7e97f890d9331bdd79857e70f6c6ea9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853485
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704771}
--
wpt-commits: 22944ce46c693c9e6cb95288b166a060cf4d8059
wpt-pr: 19630
Automatic update from web-platform-tests
Fix ChromeDriver acceptInsecureCerts capability tests (#19584)
PR #19402 added acceptInsecureCerts capability to Chrome configuration
by default. This causes failures in tests that explicitly check this
capability. Fixing by removing the default acceptInsecureCerts
capability during new_session tests.
--
wpt-commits: 8048ad3955ea3e483656a5cc413ceffd3a4b7c06
wpt-pr: 19584
Automatic update from web-platform-tests
Using device serial when using adb.
The Android device serial number, specified by the --device-serial
command-line option, was unused by the android_webview wptrunner.
This resulted in adb failing with the following error:
adb wait-for-device
error: more than one device/emulator
Bug: None
Change-Id: I85e236297d7e83950ac26a9283bdad4ef642d62c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845486
Commit-Queue: Chris Mumford <cmumford@google.com>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704747}
--
wpt-commits: 0e1c5dfb856eac565d794b2e831ce3e10cdd06f6
wpt-pr: 19583
Automatic update from web-platform-tests
Port viewport-unit-interpolation.html to wpt
The test is actually using width interpolation to test that the 'vh'
value is computed correctly.
Bug: 900581
Change-Id: Icfffb6bd06e1d89a25110727fab8b3107f2c5613
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852580
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704718}
--
wpt-commits: 7f34b9aa8c7553942551da1e9c238f0df61f417c
wpt-pr: 19624
Automatic update from web-platform-tests
Update UI when changing input's value with setAttribute
This patch fixes a bug where setting a range input element's default
value with setAttribute('value', defaultValue) does not update the UI of
the range input to show the new default value.
The bug is present in WebKit, but not present in Firefox.
Bug: 852938
Change-Id: Ibef8c0c6cefeb221a0d9220a966b04a03d815c76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834647
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704667}
--
wpt-commits: a8797562829ef022ee4a0b74ce0aeca25953f6d9
wpt-pr: 19498
Automatic update from web-platform-tests
Move common/form-submission.py to a more specific location
Part of #17913.
--
wpt-commits: 2e7681079e6018c5d5b663480fbc13da2afacbdd
wpt-pr: 19617
--HG--
rename : testing/web-platform/tests/common/form-submission.py => testing/web-platform/tests/html/semantics/forms/form-submission-0/resources/form-submission.py
Automatic update from web-platform-tests
Still test interface members when they have namespace clashes (#19611)
--
wpt-commits: e501cacc172f9ee2485d27e8d3be154425be9cb8
wpt-pr: 19611
Automatic update from web-platform-tests
[css-lists] Add list-style-type: <string>
This patch extends the syntax of the list-style-type property to accept
arbitrary string values in order to customize the marker contents.
I have followed the same approach as https://crrev.com/c/879135 did for
the display property. When a string is specified for list-style-type,
the patch sets it to a special EListStyleType::kString, and the string
is stored in an extra field. As a result of this split, list-style-type
doesn't use as much auto generated code now, e.g. EListStyleType is not
automatically generated.
Intent to Implement and Ship: list-style-type: <string>
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GojYpoeDbqc
Spec: https://drafts.csswg.org/css-lists/#valdef-list-style-type-string
Bug: 687946
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-002.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-003.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-004.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-005a.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-005b.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-006.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/parsing/list-style-type-computed.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/parsing/list-style-type-valid.html
TEST=third_party/blink/web_tests/external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/lists-3/list-style-type-string-001a.html
TEST=third_party/blink/web_tests/external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/lists-3/list-style-type-string-001b.html
This patch makes some ::marker tests in css-pseudo fail, but this is
expected because ::marker has not been implemented yet.
Change-Id: I5743b99bc1a8e66679235874623c82650860ea29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841472
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704563}
--
wpt-commits: 2178f726ee4fe4a46c98c06c931f142f542b0eb7
wpt-pr: 19542
Automatic update from web-platform-tests
Reland CompressionStream
Implement compression for "gzip" and "deflate". The implementation is
hidden behind the ExperimentalCompressionStream flag.
For unit tests, we compress and stream and uncompress it with pako, and
we make sure its output is the same as our original data.
The original CL was reverted in
https://chromium-review.googlesource.com/c/chromium/src/+/1849376
due to failures on the MSAN and leak bots.
The compression-stream.any.js test has been modified from the original
version of this CL to improve performance, and also marked as slow.
TBR=kinuko
Bug: 999091
Change-Id: I3952f500cd1ea614397fdf47771e037546583a16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851584
Reviewed-by: Adam Rice <ricea@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704544}
--
wpt-commits: 9f33ed0b72ba22b180147ca4f4ed6e2cf8eb800c
wpt-pr: 19614
Automatic update from web-platform-tests
Move common/entities.json to a more specific location
Part of #17913.
--
wpt-commits: 7c15d5b4e87b3a20ca2bc523b33303131510bc01
wpt-pr: 19599
--HG--
rename : testing/web-platform/tests/common/entities.json => testing/web-platform/tests/html/the-xhtml-syntax/parsing-xhtml-documents/support/entities.json
Automatic update from web-platform-tests
Translate the scroll coordinate to ScrollOrigin
Currently, the value of ScrollLeft / ScrollTop / ScrollTo for a box in
Element is the offset to the origin of ScrollableArea(left-top corner).
This behavior isn't consistent with Document-scroll or the behavior of
other vendors either whose origin is ScrollOrigin. There're compatibility
problems when the box has leftward or upwards scroll overflow direction.
According to the Specification, the scroll x-coordinate of a leftward box
is nonpositive, and the scroll y-coordinate of an upwards box is also
nonpositive. With using the origin of ScrollableArea, the coordinate
is always nonnegative.
In order to fix it, this patch transforms the scroll coordinate of a
box in Element interface to use ScrollOrigin as its origin.
There are a few cases needed to recalculate the scroll coordinate to
meet this change. Since the origin of scroll coordinate transforms
from the ScrollableArea origin to ScrollOrigin(), current_coordinate
is equal to old_coordinate - ScrollOrigin. E.g.
current_scrollLeft = old_scrollLeft - ScrollOrigin().X().
This behavior is guarded by a feature flag.
See intent to ship blink-dev thread:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/7X2CKPGeEa0
Bug: 721759
Change-Id: I0ceed62e6845c6e5cd976e59b36f292d60bb669c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1700001
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Frédéric Wang <fwang@igalia.com>
Commit-Queue: cathie chen <cathiechen@igalia.com>
Cr-Commit-Position: refs/heads/master@{#704470}
--
wpt-commits: 3001893957895fe522dee392b50deb6fde64d7d0
wpt-pr: 17851
Automatic update from web-platform-tests
Fix webxr test and sample references to supportsSession
Since supportsSession is removed from the spec, convert external webxr
wpt's that rely on that method to internal tests while that method is
deprecated but but still implemented. Update browser tests and sample
pages to use the non-deprecated method as well.
Bug: 1009052
Change-Id: I30249e38828726b31668b609a491792ef17c22ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850361
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704372}
--
wpt-commits: ce015c1b52fafc4de1d43f43e6ae27c100f5600c
wpt-pr: 19605
Automatic update from web-platform-tests
Unskip testdriver Actions infra tests (#19497)
The offending test has been fixed in https://github.com/web-platform-tests/wpt/pull/19555.
--
wpt-commits: 8f21bdd2710f97b928cbe909f20adcfbc072b13c
wpt-pr: 19497
Automatic update from web-platform-tests
Load Ahem as a web font in css-shapes tests. (#19577)
This makes font setup/restoration explicit rather than per-subtest.
This allows us to setup Ahem usage, then wait for fonts to load, and
then run all computed tests as a discrete block.
The previous method (which dynamically inserted Ahem prior to a subtest
and removed it immediately after) didn't allow us to wait for the web
fonts to be loaded because the test page would have no Ahem usage
present at the time we waited for the fonts.ready event.
--
wpt-commits: 4c1bbd4b27cfa527485d4f56609895c9df55212b
wpt-pr: 19577
Automatic update from web-platform-tests
Let `create_release` implicitly create the merge_pr_* tag
Per https://developer.github.com/v3/repos/releases/#create-a-release,
`target_commitish` is used to create the tag, and ignored if the tag
already exists.
--
Let `create_release` publish only after uploading assets
This makes tagging and releasing almost atomic, at most leaving behind
a draft release if something goes wrong. Because no tag or (non-draft)
release will be created in case of error, the script can just be run
again without first removing the bad release.
--
Use PATCH method for editing a release
https://developer.github.com/v3/repos/releases/#edit-a-release
--
wpt-commits: 805c75b7fc049f0f3d332f842f688db46533298f, 14f032147ff36be6e6123a4cf4c0d365fe564e57, f60b9f7ec3da5f7de0cb469b05be4d8886a06b98
wpt-pr: 19593
Automatic update from web-platform-tests
Move common/css-red.txt to more specific location
Part of #17913.
--
wpt-commits: fb43a7b4bd4f97f050eb9296e003d47e93cea42c
wpt-pr: 19598
--HG--
rename : testing/web-platform/tests/common/css-red.txt => testing/web-platform/tests/html/semantics/document-metadata/the-style-element/support/css-red.txt
Automatic update from web-platform-tests
Revert "CompressionStream"
This reverts commit 6e443093073dcea5c3ee85257f82e7c4433198f3.
Reason for revert: Causes failures on WebKit Linux Leaks and Webkit Linux MSAN, see https://crbug.com/1012652
Original change's description:
> CompressionStream
>
> Implement compression for "gzip" and "deflate". That implementation is
> hidden behing ExperimentalCompressionStream flag.
>
> For unit tests, we compress and stream and uncompress it with pako, and
> we make sure its output is the same as our original data.
>
> Change-Id: I89dde0e06a07b695be93a3b4f81fa6b3ee80d760
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1763344
> Commit-Queue: Adam Rice <ricea@chromium.org>
> Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
> Reviewed-by: Adam Rice <ricea@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#704009}
Bug: 1012652
TBR=kinuko@chromium.org,ricea@chromium.org,yhirano@chromium.org,robertma@chromium.org,acomminos@fb.com,arenevier@fb.com
Change-Id: I3d57975faa0206478048f518b53dcb617192b016
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849376
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704123}
--
wpt-commits: e710d1d6bbe007a6a9344f79e17b445cf97cc623
wpt-pr: 19592
Automatic update from web-platform-tests
Use `zstd -q` in manifest_build.py (#19588)
gzip and bzip2 are silent by default.
--
wpt-commits: 2d84e4d2cc6d881d0abd7d968a7709a18b309f3a
wpt-pr: 19588
Automatic update from web-platform-tests
Remove extra double quotes in manifest_build.py (#19560)
There's no shell escaping at this layer, so these quotes were treated
as literal and included in the release body.
This also simplies the code by using --format=%B.
--
wpt-commits: be08de67a0b21e800cc263e319aa4f17034bae53
wpt-pr: 19560
moz-wptsync-bot
Hiroshige Hayashizaki
Philip Jägenstedt
Kevin McNee
Mike West
Mike Pennisi
Parastoo Geranmayeh
Pablo Saavedra
Luke Zielinski
Fergal Daly
Carlos Alberto Lopez Perez
autofoolip
James Graham
Rakina Zata Amni
kaixinjxq
Wanming Lin
Marina Sakai
Florian Rivoal
Peter Linss
Vladimir Levin
Lukasz Anforowicz
Tiger Oakes
Koji Ishii
Fredrik Söderquist
Olga Gerchikov
Sertay Sener
Philip Rogers
Yifan Luo
John Chen
Anne van Kesteren
Alexey Shvayka
Morten Stenshorne
Raphael Kubo da Costa
Rob Buis
Sam Sneddon
Francois Beaufort
_Ros_
marmeladema
David Grogan
Eric Willigers
Darryl Pogue
Leon Han
Stephen McGruer
Oriol Brufau
Rune Lillesveen
Nick Burris
Daniel Vogelheim
Victor Costan
Chris Mumford
pyup-bot
Simon Pieters
Xida Chen
Joey Arhar
Luke Bjerring
Adam Rice
Cathie Chen
Alex Cooper
Todd Reifsteck
Dominik Röttsches
Bnaya Peretz