Automatic update from web-platform-tests
FindKeyframesRules should use originating element.
It's only using the TreeScope to find @keyframes in which case using the
originating element for pseudo elements should work. Even better when
the originating element is a shadow host, so that we look up :host rules
from the shadow tree for :host::before { animation-name: anim }.
Bug: 961941
Change-Id: I38edec156eaaa7cfb3680762b135323deae00a68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2162988
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762791}
--
wpt-commits: 245ed57a5e400fff2dc4adbf8e452d64397399cd
wpt-pr: 23222
Automatic update from web-platform-tests
Forward CSP, even for the initial empty document.
Bug 1064676 has been fixed by:
https://chromium-review.googlesource.com/c/chromium/src/+/2111170
And tested by:
https://chromium-review.googlesource.com/c/chromium/src/+/2144012
The bug was fixed for every CSP checked in the renderer process. However
there are still an issue for the one checked in the browser process. It
turns out the CSP in the initial empty document weren't properly
propagated to the browser process.
This patch:
1) Fix the bug by sending the CSP of the initial empty document.
2) Add a regression test (WPT).
This patch can potentially also fix:
- https://crbug.com/1072719
- https://crbug.com/955350
(I haven't checked. I will do it later after landing this patch)
Bug: 1064676, 1072719, 955350
Change-Id: Ie5325035c74d9e2476d6c80af3e5d5c9068ea928
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159242
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762769}
--
wpt-commits: 7179786e28b8266789355518b65b8df65aa962c2
wpt-pr: 23144
Automatic update from web-platform-tests
Migrate pointerevents/mouse-on-object.html to wpt
The expected behavior on this test seems to be a
hack as it implicitly captures mouse to the object
and still sends the mouseup/pointerup to the object
when down happened on the object even though up is
happening outside of the object. This seems to
resolving compat issues on embedded flash objects.
Change-Id: Ibd888a989dbcf5e6ff08b35569903967edc957e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2160142
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762476}
--
wpt-commits: 55367a4c706fa32301980773cb2c09cbcd291635
wpt-pr: 23174
Automatic update from web-platform-tests
for larger tables on mobile, you have to wrap in a div
and set overflow to auto so that they'll scroll the div instead of the window
--
wpt-commits: 5e7cbed423a3040dc8ca50359dd033a46dba5cf4
wpt-pr: 23254
Automatic update from web-platform-tests
[device-orientation] Simplifies tests by using EventWatcher
This CL simplifies wpt/orientation-event tests by using
testharness.js' `EventWatcher` to replace existing customized
`waitForEvent` method and improving event comparison methods.
Uses `setGetSensorShouldFail` to simulate UA can not provide
sensor information for orientation/deviceorientationabsoluteevent.https.html,
and merges which into orientation/basic-operation-absolute.https.html.
Bug: 816462
Change-Id: Ia7bf83cb9401265722e472ccdd01adc114eff660
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154389
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Cr-Commit-Position: refs/heads/master@{#762675}
--
wpt-commits: 44915d53e1747700990f4f03442040e59cd2da19
wpt-pr: 23100
Automatic update from web-platform-tests
Implement and ship 'ruby-position' CSS property
This CL implements 'ruby-position' CSS property, which is a property
independent from the existing '-webkit-ruby-position', but these
properties share a single ComputedStyle field.
We apply neither legacy name alias [1] nor legacy shorthands [2] because
- Acceptable keyword sets are different in ruby-position and
-webkit-ruby-position.
- Avoid behavior changes with |element.style.webkitRubyPosition =
'after'|.
* core/css/css_computed_style_declaration.cc
Add 'ruby-position' to getComputedStyle() enumeration.
* core/css/parser/css_parser_fast_paths.cc
Add setting for fast-path parsing
* core/css/properties/longhands/longhands_custom.cc
Add CSSValueFromComputedStyleInternal() to translate a ComputedStyle::
GetRubyPosition() value to 'over' or 'under'.
* core/css/resolver/style_builder_converter.{h,cc}
Add a function to convert a parsed CSS keyword to a
blink::RubyPosition value.
* web_tests/external/wpt/css/css-ruby/ruby-position.html
New test to check ruby annotation position.
* web_tests/fast/ruby/ruby-position-om.html
New test to check relationship between ruby-position and
-webkit-ruby-position.
Approved intent: https://t.co/nmCPv0Onhk
[1] https://drafts.csswg.org/css-cascade/#legacy-name-alias
[2] https://drafts.csswg.org/css-cascade/#legacy-shorthand
Bug: 196690
Change-Id: I2f00099f90a2222b7ddba8b58c3a532f3b997744
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152569
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762664}
--
wpt-commits: ae457cd8b39790508e841f581e2066871859db1a
wpt-pr: 23221
Automatic update from web-platform-tests
Update two SVG tests to be consistent between browsers (#23240)
svg/import/pservers-grad-08-b-manual.svg:
This test renders some text using a font that doesn't contain the space glyph.
However, the content contains the space character, and doesn't specify a fallback
font. This means that different browsers on the same OS will pick different
fallback fonts, causing different renderings. Instead, the test should be updated
to specify a fallback font, which makes browsers render it consistently.
imported/w3c/web-platform-tests/svg/import/text-altglyph-01-b-manual.svg:
Similarly, this test renders text with a font that doesn't support those characters.
(It does it using <altGlyph>, but support for <altGlyph> has been removed in SVG 2.0
and neither Safari nor Firefox support it.) A fallback font should be supplied to the
test to get consistent renderings across browsers.
Co-authored-by: Myles C. Maxfield <mmaxfield@apple.com>
--
wpt-commits: 51151cf5bfc32adb8d96fca51a30c126d1e0200d
wpt-pr: 23240
Automatic update from web-platform-tests
bluetooth: Split bluetooth-helpers.js
This change splits the bluetooth-helpers.js files in two. The new
bluetooth-test.js file contains methods for setting up the web tests and
for asserting conditions. The bluetooth-helpers.js file now contains
helper methods that set up fake Bluetooth devices for use in the Web
Bluetooth tests.
I added JsDoc style comments to the helper methods to make it clear
what kinds of objects are expected as parameters and what the methods
will return. I also reordered the bluetooth-helpers.js methods so that
they are defined before they are used.
Bug: 1070816
Change-Id: Ib5215555be2b24b11f8dea9098d83ad69719a284
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2149909
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: James Hollyer <jameshollyer@google.com>
Commit-Queue: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762594}
--
wpt-commits: 6f8f0b30a4af91762427b4ff528ed344d5636c6d
wpt-pr: 23157
Automatic update from web-platform-tests
[EventTiming] Implement durationThreshold
This CL implements a durationThreshold member of PerformanceObserverInit
which enables setting a threshold for the event timing entries received
by a PerformanceObserver. The entries are still buffered per the default
duration threshold of 104 for now. Tests are added for various threshold
values. PR: https://github.com/WICG/event-timing/pull/82
Bug: 543598
Change-Id: Id3407ddbcd1713fc33036518bbf88696add423cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159611
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762168}
--
wpt-commits: c7f5f1561f751232d7577d21808e45af289a2d46
wpt-pr: 23152
Automatic update from web-platform-tests
Be responsive to reference box changes for transformed containers
This adapts the technique used elsewhere to work with
LayoutSVGContainers (specifically LayoutSVGTransformableContainer).
Bug: 697052, 1074080
Change-Id: I5dc1ca440aaa2d76eb49ae54fb0c4422f166c4f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165107
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762562}
--
wpt-commits: 15f0671b0ebffbe0d7fd64fdbdb4f2e69fb0eb3e
wpt-pr: 23233
Automatic update from web-platform-tests
Account for root element paint offset when painting backgrounds
The root background is painted from the coordinate space of the root
element, but expands to fill the viewport. The difference between these
spaces needs to be used as an offset when painting the background.
For the non-transform case, this patch removes the paint offset
adjustment made to the entire paint rect in ViewPainter, and only
applies the paint offset for positioning the background in
BackgroundImageGeometry::ComputePositioningArea. This way, painting
starts from the origin, without paint offset.
For the transform case, paint properties will apply the paint offset,
and the entire paint rect needs to be adjusted to remove the paint
offset. This patch specifies the transform state of the view and root
element, and uses GeometryMapper to map the background paint rect into
the coordinate space of the root element.
A TODO has been added to more clearly specify the non-transform
and transform cases.
Bug: 1071957
Change-Id: Iedc1834ef9c400340b668b3eec73a0f3f4506194
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161350
Auto-Submit: Philip Rogers <pdr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762543}
--
wpt-commits: f8bd87deb2c2a0ea974adb6c64ef013a60188193
wpt-pr: 23234
Automatic update from web-platform-tests
Create LayoutShiftAttribution objects in LayoutShiftTracker.
Also mark the REF "experimental", so that it is tested, and add a test.
Bug: 1053510
Change-Id: I8bac9c8002d20991599a1bf396f28dd9101b0f63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157988
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762442}
--
wpt-commits: a7b88cb7b8ba75a5399aee54540f03bb88924672
wpt-pr: 23220
Automatic update from web-platform-tests
WPT Chromium logger bug fixes to integrate with results viewer.
Three main issues fixed here:
1. Removing a trailing whitespace in the "expected" field. This is
caused by "known_intermittent" always being present in the test_end data
dict, but simply being empty when no intermittent statuses exist.
2. Making sure the start timestamp is always in seconds - the wpt test
framework provides it in microseconds, but we can fallback to "now"
which returns seconds.
3. All artifacts are expected to be lists.
Bug: 1070265
Change-Id: I3dc98f8e37d847727c3165ab51c293f529d3c5eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163065
Commit-Queue: Robert Ma <robertma@chromium.org>
Auto-Submit: Luke Z <lpz@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762415}
--
wpt-commits: 01aed092cae7983b2d4ecf29097e33ce4e9af5b9
wpt-pr: 23211
Automatic update from web-platform-tests
Mark clipboard-apis/async-idlharness.https.html as timeout=long
This is symptomatic of crbug.com/1047818, but to stop the pain for
sheriffs lets mark it timeout=long for now.
Bug: 1073055
Change-Id: I1e17f6a0fe2dc66f4c842b80361057cb19a3edc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163955
Reviewed-by: Luke Z <lpz@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762348}
--
wpt-commits: a6396b8566a7a85fa2ce33abfc480cc7e48574aa
wpt-pr: 23227
Automatic update from web-platform-tests
Use assert_implements in test the-input-element/type-change-state.html (#22145)
* Use assert_implements to check if the browser supports both input
element types before trying to change the state from one to other.
* For example, WebKitGTK and Safari doesn't support several of the input
types tested here (like those related to dates). The output of the test
its clearer if the precondition its checked before.
--
wpt-commits: af8fb743e877884ae9f6cec97a60da6e22d06740
wpt-pr: 22145
Automatic update from web-platform-tests
[client hints] Fix handling of redirects in navigation
In particular, the browser needs to handle accept-ch there since
the renderer doesn't see the intermediate steps until after everything
is fetched, and new client hints may be requested in the middle of the
chain. This is done by having the network service parse the header
and store in ParseHeaders, then using that in the browser
This is also likely the first step towards moving more of handling
of accept-ch to browser (which will simplify some things and fix
some bugs).
Bug: 1050726
Change-Id: Ie02d7492c02b75034b36af30e489ebbb430d6a1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2085114
Commit-Queue: Maksim Orlovich <morlovich@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762329}
--
wpt-commits: 39411b7ef888f9bd67e430970042f757bac0bed0
wpt-pr: 22068
Automatic update from web-platform-tests
[css-flexbox] Implement gap/gutters
This only works when you enable "Enable experimental web platform
features" in about:flags.
This patch doesn't implement a weird case that firefox supports:
resolving a percent column-gap when the flexbox's height is indefinite.
This patch resolves it to 0. We may wait until that is fixed before
exposing this to the web without the about:flag. The relevant test is
http://wpt.live/css/vendor-imports/mozilla/mozilla-central-reftests/flexbox/flexbox-column-row-gap-004.html
The spec issue is https://github.com/w3c/csswg-drafts/issues/4664.
This patch does not include the few engine-specific bits in legacy, so
gap only works in FlexNG.
Change-Id: I691889cf4b9346e94c83ef655dc9fd6eebca640d
Bug: 762679, 845235
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2162149
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762264}
--
wpt-commits: 344e2aa99d6555e12d0003fb6cbf7abf0c5fd64a
wpt-pr: 23194
Automatic update from web-platform-tests
Add multi-host test case for declarative Shadow DOM
This case was not previously tested.
Bug: 1042130
Change-Id: I5874bc08abba57b6d5150ab8ae772ecec6113b19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161767
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762045}
--
wpt-commits: 13868f2aa3ff16f7f338d492e0027c301f07f74c
wpt-pr: 23212
Automatic update from web-platform-tests
[@property] Add tests for @property and CSS Typed OM
The @property rule is relevant for CSS Typed OM, because the syntax of
a registered custom property can now be changed several times, or even
revert back to unregistered. This affects how values should reify.
Bug: 973830
Change-Id: I0ad5ba843b89d9153657e8b3f464e2dd33659cd2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2160894
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762081}
--
wpt-commits: 37df62b2f9df04ad5202db498f9a6fe1d891a106
wpt-pr: 23198
Automatic update from web-platform-tests
Increase timeout for wpt...CSS2...line-height-interpolation.html
This test was running with an average speed close to its timeout and
was occasionally exceeding it, causing flakes. Marking it as slow as
per wpt guidelines.
Bug: 1073460
Change-Id: I2028d64ed727242ec3873c5172a08ecebbc45a73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163395
Commit-Queue: George Steel <gtsteel@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762061}
--
wpt-commits: e4040c2f7748ba77d996fc85e51499fadfd63eda
wpt-pr: 23210
Automatic update from web-platform-tests
[@property] Add tests for @property and transitions
This CL adds tests to ensure that transitions work as expected with
@property. The most "unique" case related to @property is perhaps that
re-declaring a custom property with a different initial value can
actually start a transition.
Bug: 973830
Change-Id: Ib97837e6dcf53af7fbfbaa8ff258d3e3041001eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161825
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#762057}
--
wpt-commits: c273058529a265c168afe05888104652babbe5d8
wpt-pr: 23199
Automatic update from web-platform-tests
Mark external/wpt/quirks/unitless-length/no-quirks.html timeout=long
This runs at 5-6s in the Chromium CQ, and occasionally tips to 7s, which
then times out.
Bug: 1069117
Change-Id: Ied941b276a59edec98cd12441b68ed0a1ac7a931
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161894
Auto-Submit: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Luke Z <lpz@chromium.org>
Reviewed-by: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761901}
--
wpt-commits: 468095972995ebf1932b263911c43b343e4391b5
wpt-pr: 23188
Automatic update from web-platform-tests
Mark a bunch of idlharness tests as timeout=long
These are all symptomatic of crbug.com/1047818, but to stop the pain for
sheriffs lets mark them timeout=long for now.
Bug: 1068574, 1065250, 1070562, 1073055
Change-Id: I76e29d3037bd0c98c96bf21a7427d7981b91def4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161728
Auto-Submit: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761981}
--
wpt-commits: a5d1774ecf41751d1c9357c27c709ee33bf3e279
wpt-pr: 23191
Automatic update from web-platform-tests
Initialize start time of scroll animations to zero.
Implemented web-animations-1 spec changes introduces in [1].
- Update play and pause procedures to initialize start time of scroll
animations to zero.
- Updated calculate play state procedure to return "running" state for
animations that has start time resolved.
- Added/modified tests reflecting spec changes.
[1] https://github.com/w3c/csswg-drafts/pull/4842
Bug: 1070637
Change-Id: Ic83995899b2f3f8d8f985f84b8a2b438bbad7c35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2150687
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761974}
--
wpt-commits: 46978682c5d3e2ff08468be05564307a9a75e06b
wpt-pr: 23145
Automatic update from web-platform-tests
XHR: correct 303 redirect logic
And add a relevant case for it.
--
expected results were wrong for some tests
--
wpt-commits: c814858d49abf943734fb28e0a13747ef875e49b, ad7bb0fa63d2e68646842a99b75a97270436e571
wpt-pr: 23176
Automatic update from web-platform-tests
[@property] Improve test coverage for valid/invalid rules
This adds new tests that verify that invalid rules are ignored,
and don't affect other valid rules.
I also rewrote this test file to use utils.js more liberally. It makes
individual tests harder to understand for the uninitiated, but it
scales so much better as the number of test functions increases.
Bug: 973830
Change-Id: Ie19d85042a0475180cc4bbee4ad202ea08adba73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161005
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761969}
--
wpt-commits: 594e55b48c52c20ab5806b9e60b8cfcc742c5ae6
wpt-pr: 23167
Automatic update from web-platform-tests
WASM JS API: Test new Web IDL class string behavior
Follows https://github.com/heycam/webidl/pull/357.
--
wpt-commits: 72952afb3d1ac4eff5ca41de29f42007d4bb23aa
wpt-pr: 23205
Automatic update from web-platform-tests
[taskcluster] Actually use the new image in tests
This is a follow-up to #23190. I forgot that tools/ci/tc/tasks/test.yml
existed, so we really only updated the image of the decision task.
Drive-by:
* Update README to document this.
* Remove python3-pip from `install` as it's now included in the image.
--
wpt-commits: 50adb7c97b79cfd2907dbb506a0f74b59560124e
wpt-pr: 23208