Automatic update from web-platform-testsDOM: retarget relatedTarget
relatedTarget gets retargeted. Also use test rather than async_test if possible.
Fixes#10854.
--
wpt-commits: b9f5402f16fa98c88428dace0a7088ef9dae8df3
wpt-pr: 10863
Automatic update from web-platform-tests[KeyboardMap] Initial stub for navigator.keyboard.getLayoutMap
This includes the WebIDL defs, initial WebPlatformTests and mojom
over to stubs in the RenderWidgetHost.
Spec: https://wicg.github.io/keyboard-map/
A proper implementation for this API will be in follow up cls,
a separate cl per platform.
Bug: 832811
Change-Id: I17dee21095665739a3f1986e48a2182d6b6fab00
Reviewed-on: https://chromium-review.googlesource.com/1014244
Commit-Queue: Gary Kacmarcik <garykac@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556639}
--
wpt-commits: d9587de4ff827d75fefbd72f42e834078094202d
wpt-pr: 10495
Automatic update from web-platform-tests[Picture-in-Picture] Resolve promises when window is created and closed.
This makes the promise returned by enterPictureInPicture() resolved only
when window is created. Picture-in-Picture window size is still
hard-coded though and will be fixed in a future CL.
This also makes the promise returned by exitPictureInPicture() resolved
only when window is closed.
Bug: 806249
Change-Id: I8232a42a50b808527560eb0e6a69d8fb98da63e4
Reviewed-on: https://chromium-review.googlesource.com/1025832
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: apacible <apacible@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/master@{#556567}
--
wpt-commits: 6d541700e3dca7a46672f440afcbba225930b648
wpt-pr: 10604
Automatic update from web-platform-testsAllow 0% in font-stretch
Per https://github.com/w3c/csswg-drafts/issues/2591, 0% should be an
allowed value in font-stretch. Remove the check that percentages are >=
0 for font-stretch, as any negative non calc values are already rejected
by kValueRangeNonNegative. Also update a test of valid calc values in
font-stretch, as even though they are outside the allowed range, they
should not be subject to parse-time constraints.
Bug: 834236
Change-Id: I0e728d8cc89b45bac7be956a7662533d4775c511
Reviewed-on: https://chromium-review.googlesource.com/1046926
Commit-Queue: Chris Nardi <cnardi@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556568}
--
wpt-commits: bbb732773d07230e07f95c551e09b851d450effa
wpt-pr: 10866
Automatic update from web-platform-testsAdd web platform tests for the new client hints
Add tests for "rtt", "downlink" and "ect".
Bug: 835333
Change-Id: If54c01612f10e96f7b37868e19b01a7ff3266d43
Reviewed-on: https://chromium-review.googlesource.com/1045917
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556532}
--
wpt-commits: 6f03878da8255e23699c5d45e98dd123ef88383a
wpt-pr: 10874
Automatic update from web-platform-testsOverride 'touch-action' for 'vertical-scroll'
With "vertical-scroll 'none'" as a feature set for an <iframe>, we want
to make sure the <iframe> cannot prevent the user from vertically
scrolling the page. One way of blocking user is to exclude "pan-y" from
"touch-action".
This CL makes sure that when an element is inside such frames, the
"touch-action" always includes "pan-y".
Link to explainer/design document:
https://docs.google.com/document/d/1qiWelnMlsOHuT_CQ0Zm_qEAf54HS5DhoIvEDHBlfqps/edit?usp=sharing
Bug: 611982
Change-Id: Ie60c665de3c82ec2438bcea10f56b54d51084eda
Reviewed-on: https://chromium-review.googlesource.com/1014389
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556484}
--
wpt-commits: 549a93f3aa84166e5df3400cb53b35aa84f383e8
wpt-pr: 10718
Automatic update from web-platform-testsUpdate WPT test: url-in-tags.window.js
The web-platform-test: FileAPI/url/url-in-tags.window.js relies on the
load event to be dispatched after the page has scrolled to the anchor.
This is not guaranteed. It is currently non-deterministic in Chrome.
The page: https://scrolly-in-onload-event.glitch.me/ shows a case where
the opposite happens.
Doing task https://crbug.com/831155 caused this test to fail.
Note: This test was working only on Chrome.
Current status: https://wpt.fyi/FileAPI/url/url-in-tags.window.html
There is a chance applying this patch will make it work on Safari as
well.
Related CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1042191
Bug: 831155
Change-Id: Ifa3f8e3d35cdb2635261248c3c9e9fd959f44340
Reviewed-on: https://chromium-review.googlesource.com/1046596
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556479}
--
wpt-commits: d353ff8898fdbb0e9d909c081d1a42d67e75b804
wpt-pr: 10864
Automatic update from web-platform-tests[css-grid] Avoid layouts during intrinsic size computation
The definition of intrinsic size excludes explicitly performing layouts
to compute the final value. However, it may be necessary to laid out
some children to retrieve accurate information about the geometry of
the box, specially when some of these children are orthogonal to the
box its intrinsic size is being computed.
However, the writing-mode specification suggest [1] that auto-sized
orthogonal boxes may require to run their sizing phase before any
content contribution could be established.
The Blink engine discourages performing layouts during intrinsic size
computation. In order to address the orthogonal flow issues and get
a more accurate sizing, both during intrinsic size and layout phases,
the engine performs a pre-layout of all the orthogonal boxes in the
layout tree (LocalFrameView::LayoutOrthogonalWritingModeRoot).
However, this pre-layout operations doesn't make sense for grid items
because the grid areas, the grid items' actual containing blocks, are
not computed yet. Hence, we decided to exclude grid items from this
pre-layout operation (PrepareOrthogonalWritingModeRootForLayout).
With this CL, we follow the same plan Blink has for orthogonal flow
boxes, but doing it once the grid items are placed in their
corresponding grid areas. Since the grid tracks sizing algorithm has
not been run at this stage, the size of the grid areas is estimated
based on the track's max-sizing function, in a similar way [2] the
algorithm does to deal with orthogonal items during the layout phase.
This change is covered by current tests, however, added an additional
test to verify we use the max-track sizing as a way to estimate the
orthogonal item's block-axis size.
[1] https://www.w3.org/TR/css-writing-modes-3/#orthogonal-flows
[2] https://drafts.csswg.org/css-grid/#algo-overview
Change-Id: I836b92120825916324f94befec6d35263ec84f2b
Reviewed-on: https://chromium-review.googlesource.com/1027882
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#556469}
--
wpt-commits: a878a9a9a5d1f4b0160620ba5479ba2c7d2e2373
wpt-pr: 10810
Automatic update from web-platform-testsAdds a test for basic WebRTC video codec conformance.
This tests that the browser conforms to RFC 7742, "WebRTC Video
Processing and Codec Requrements".
It establishes a new subdirectory for protocol-related WebRTC tests.
Bug: chromium:839753
Change-Id: Ia4795c4532fb74ae76e6a47329a41807479113c5
Reviewed-on: https://chromium-review.googlesource.com/1043886
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556454}
--
wpt-commits: 644351d8f6c20a562f5d34dcbbb4f3ea416fadcf
wpt-pr: 10841
Automatic update from web-platform-testsAdd annevk to dom/OWNERS
I should probably help out here.
--
wpt-commits: d46cd6b9827d56c4cd380ea4ffa005df265c98a6
wpt-pr: 10869
Automatic update from web-platform-testsFix #10741: Call Out-File with an encoding for make-hosts-file on Windows (#10800)
--
wpt-commits: 6a44b23ac8630cea55ab556d43d3c61562df1654
wpt-pr: 10800
Automatic update from web-platform-testsWeb Animations: Add test for Document::getAnimations across iframes (#10291)
--
wpt-commits: b8639ae6bce07fc4ca3898a33ce11ce024786bcf
wpt-pr: 10291
Automatic update from web-platform-testsAccname: Remove unspecified behavior from test cases (#10826)
The accname spec doesn't describe exactly what should happen with respect
to whitespace insertion when inline elements are being concatenated in
a name-from-contents calculation. This will be addressed in Accname 1.2.
--
wpt-commits: 081648feab808a8b054c86387ff5ceba3317f281
wpt-pr: 10826
Automatic update from web-platform-tests[FilterContainer] Add WPT for filter establishes containing block.
Based on CL 1033824
This patch adds three tests and test the following:
- Filtered block establishes a container for fixed and abs pos.
- Filtered inline establishes a container for fixed and abs pos.
- Filtered <html> does not establish a container for fixed pos.
Bug: 795549
Tbr: vmpstr@chromium.org
Change-Id: I3fa13cc7f478503583a191bfb434cdab860862ef
Reviewed-on: https://chromium-review.googlesource.com/1045727
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556343}
--
wpt-commits: 722173b2155db21d1bcd2bab8348554b67ad7863
wpt-pr: 10858
Automatic update from web-platform-testsAdd historical tests for document.selectedStylesheetSet/preferredStylesheetSet (#10861)
These are implemented in Blink and WebKit. Note the difference in
capitalization.
--
wpt-commits: f7c251fe7d2725e4cd423c89648fbe0676502989
wpt-pr: 10861
Automatic update from web-platform-testsSupport groupId constrainable properties in MediaDevices.getUserMedia()
This CL also adds support in MediaStreamTrack.applyConstraints().
Drive-by: Minor lint fixes.
Bug: 833333
Change-Id: I8636def42d9ed64c6f58777d44343e569e541bfb
Reviewed-on: https://chromium-review.googlesource.com/1021570
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556124}
--
wpt-commits: 23a93d234f1f9fc681cdee1d0c05c38070910da2
wpt-pr: 10554
Automatic update from web-platform-testsFetch: couple minor improvements to some CORB tests
--
wpt-commits: 42b23a6173024df2f7158bc1165c8b71e908b0f5
wpt-pr: 10846
Automatic update from web-platform-testsBaseline of inline-block for different values of overflow, for an errata to CSS2 (#7579)
* Test for errata http://www.w3.org/Style/css2-updates/REC-CSS2-20110607-errata.html#s.10.8.1 (baseline of inline-block)
* Typo in rel=author link.
--
wpt-commits: 62a50ada791ff3dfb6a660fa33ad8a9dc1a8e423
wpt-pr: 7579
Automatic update from web-platform-tests[Layered API] Implement std:async-local-storage behind a flag
This CL imports the async-local-storage implementation as-is
except for renaming to index.js.
Original author:
Domenic Denicola (domenic@chromium.org)
https://github.com/domenic/async-local-storage
All code were written and contributed by Googlers
who are Chromium Contributors.
Tentatively this CL imports the files under core/script/resources
until a long-term plan for repository location etc. is settled.
This is a still experimental feature behind a flag, and its
API interface and implementation can be changed significantly
before shipped.
This CL also imports a test with some modifications.
Change-Id: I99944c75240ab2f1d114aa85f5c8ffac1f5e9b98
Reviewed-on: https://chromium-review.googlesource.com/1033713
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555967}
--
wpt-commits: 21779ed0b53a409d2b0a8c8ca5ab897e3326e2e0
wpt-pr: 10744
Automatic update from web-platform-testsHandle some html/js polyglots in CORB confirmation sniffing.
Cross-Origin Read Blocking (CORB) tries to protect certain resource
types (e.g. text/html). To be resilient against HTTP responses
mislabeled with an incorrect Content-Type, CORB sniffs the response body
to confirm if it truly is the protected type.
Before this CL the confirmation sniffing logic decided to block
resources that are both a valid html and a valid javascript.
Blocking of such resources is undesirable, because it is disruptive to
existing websites that use such polyglot responses in <script> tags.
After this CL, a HTML comment that contains a Javascript comment will
cause the confirmation sniffing to decide that the response is not
really a HTML document (this will prevent CORB blocking).
Bug: 839425
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ie790a81c2742513aed9fda45edd0bb2976bd0fc6
Reviewed-on: https://chromium-review.googlesource.com/1042820
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555951}
--
wpt-commits: 85cecd9725b1bc82a6e2aa6d45e287b7d383a23b
wpt-pr: 10833
Automatic update from web-platform-testsImplement AnimationEvent.pseudoElement
The spec is here:
https://drafts.csswg.org/css-animations/#interface-animationevent
A layout test is changed to test this API.
Bug: 437132
Change-Id: Ic463b19488271e1caeb78afa6120bb53f7d5e94d
Reviewed-on: https://chromium-review.googlesource.com/1019383
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555898}
--
wpt-commits: 1550fc2313eca53eec8ea88a2b024446665ea4bf
wpt-pr: 10532
Automatic update from web-platform-testsMove AudioBuffer tests to WPT
These tests either pass on Firefox or are bugs in Firefox.
Bug: 745778
Change-Id: I0a2997d5c3602f026e5cf9132a68a833c975d32d
Reviewed-on: https://chromium-review.googlesource.com/1042801
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555882}
--
wpt-commits: 29918c7e78ec3596955ae4ca42073c5b2ca65786
wpt-pr: 10829
Automatic update from web-platform-testsMove more stuff out of the docker file and into the startup script
In particular:
* Don't try to install Ahem into the docker image since this fails if
Ahem ever changes
* Do the souce checkout in the startup script. This should ensure that
subsequent wpt commands work with the latest code, and fixes some of
the intermittent errors we have seen.
--
Update to latest docker image
--
Check out the required commit directly in start.sh.
Also optimise things so we don't download Chrome unless actually required.
--
Update taskcluster tasks
--
wpt-commits: 4678331fc2b64906862aedd7ce3cdb60ebae33bb, c2158354781f86f5c9b551b2633161756548a957, f2eadc2376f99e33888380f527fffa4df13a2bca, 843547ca495bcd7b0bc5c7034e924eef7b672446
wpt-pr: 10762
Automatic update from web-platform-testsAdd run_info and timestamps to wptreport
run_info includes OS and browser info.
This is the first stab at #10511 .
--
wpt-commits: b2b367b9d21aa78f71e66f0adb9d2a73d1d3fef8
wpt-pr: 10811
