Automatic update from web-platform-tests
WebXR - mojo - rename XRReferenceSpaceCategory to XRReferenceSpaceType
This is a mechanical change to rename the mojo type and additional misc
changes requested as a followup for CL https://crrev.com/c/2203277.
Changes:
- s/XRReferenceSpaceCategory/XRReferenceSpaceType, along with renaming
few variable names from "*category" to "*type"
- changed mojo type from now-deprecated macro-style naming to
constant-style naming
- refactored few lines of code that compute reference space appropriate
for anchor creation into XRSession::GetStationaryReferenceSpace(), used
both in XRFrame and in XRHitTestResult for anchor creation
- added `using` in xr_reference_space.cc to help with readability of a
quite-long type to something shorter (`ReferenceSpaceType` instead of
`device::mojom::blink::XRReferenceSpaceType`) - same directive could be
introduced in other files but the occurrences of the offending type are
not that common elsewhere
- refactored `XRReferenceSpace::NativeFromMojo()` since 3 `case`s were
identical or very similar
There should be no functional change.
Change-Id: I8e8efdc036f11347f8d9159fbaede44634c6eb78
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2229622
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#775189}
--
wpt-commits: 70225fa88786126e19a9010fc803d95eeea0994e
wpt-pr: 23994
Automatic update from web-platform-tests
Add willReadFrequently attribute to CanvasRenderingContext2DSettings
As part of the performance improvement for read access, the
`willReadFrequently` attribute is added to
`CanvasRenderingContext2DSettings`. It's currently hidden behind the
feature flag `NewCanvas2DAPI`.
Bug: 1090180
Change-Id: I0e9f542b9b45c940d7a55f9ebf5451972492dc6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225495
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Juanmi Huertas <juanmihd@chromium.org>
Commit-Queue: Teresa Kang <teresakang@google.com>
Cr-Commit-Position: refs/heads/master@{#775157}
--
wpt-commits: 46d3e553292052deca05a3db7b8f758e6d8aa02b
wpt-pr: 23914
Automatic update from web-platform-tests
[EventTiming] Allow spurious inputs when looseCount is true
This CL is a tentative fix for some flaky tests. An assert_equals to 0
is sometimes failing, presumably because the test itself may cause some
inputs to occur. Hence, we only check that eventCounts is 0 when the
|looseCount| variable is set to false.
Bug: 1074048
Change-Id: I989ccdb7cb469ff24132bf17a3da9a43264ae6ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225293
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774650}
--
Give two event-timing tests long timeout
--
wpt-commits: 8062b6cec1efca70adb0c1ef16c4e53936328993, f9b7b656af0513874a16ccb68c6a1b2957ea086f
wpt-pr: 23925
Automatic update from web-platform-tests
[WebSocket] Test header + close frame in same packet
Modify the existing web platform test opening-handshake/005.html to send
the response header and the close frame in the same packet. This
verifies that Chrome passes the close data to JavaScript correctly in
this case.
This increases the coverage of the existing test, so there's no need to
retain the old behaviour.
Also remove the timeout expectations for this test, and make sure it
doesn't timeout on failure.
Closed: 1090210
Change-Id: I327c55d1517615511d6d71e1b464d5d3dc03b502
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2228252
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#775124}
--
wpt-commits: dc423abead2ba9d56f718bf5996e3e635e845c23
wpt-pr: 23938
Automatic update from web-platform-tests
Fix paint offset of table section background with composited transformed row
Add missing ScopedPaintState for the table row when painting table
section background behind cells, in case that the table row has
PaintOffsetTranslation needing paint offset adjustment.
Bug: 1091016
Change-Id: I82203cf2bd5392bed2cc74806e04780e708804b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2229586
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#775118}
--
wpt-commits: a7c3e215fb449cc2edc225af989cb8c9f79a034c
wpt-pr: 23970
Automatic update from web-platform-tests
Use text-decoration-thickness value in underline painting
Parsing of text-decoration-thickness was added in [1], use the parsed
value in text decoration thickness painting.
Add a WPT ref test that compares text-decoration-thickness value from a
variable font (keyword value 'from-font' for text-decoration-thickness)
with the identical rendering achieved by using a static font with thick
and thin underline metadata.
Add a second WPT ref test that compares a fixed
text-decoration-thickness value to the from-font values of a font with
thick and thin underlines.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/2178888
Bug: 785230
Change-Id: I626a321a38c77e106215b640dcf85c20f7a0ad93
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218119
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#775116}
--
wpt-commits: a58844e7f02a1b4450ba7fb0365a4f950bc32926
wpt-pr: 23891
Automatic update from web-platform-tests
Python 3: port tests in cors following migration guideline in RFC 49 (#23770)
--
wpt-commits: d0d526f74297c60873c242ab43c6af43f729128b
wpt-pr: 23770
Automatic update from web-platform-tests
Align with latest version of webrtc-stats hierarchy (#21553)
* Align with latest version of webrtc-stats hierarchy
Removed stats for stream, track (now obsolete)
Added media-source, transceiver, sender, receiver, ice-server stats
Aligned fields of various stat objects with new hierarchy
Aligned list of MTI stats with latest WebRTC spec
--
wpt-commits: ee29cde89030a59a1d59e54734a28409f5caaaf0
wpt-pr: 21553
Automatic update from web-platform-tests
[COOP access reporting] Preliminary WPT tests.
Add some basic WPT tests about the COOP access reporting feature.
No web browsers actually implement this. As a result, chrome do not
pass them yet.
The tests aren't complete yet, they will evolve along the specification
and the implementations.
Bug: 922191
Change-Id: Ie4675e5fb5ec0f839ca1527c15fafbb456925a0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2228884
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#775020}
--
wpt-commits: 093d6292689f36736e7ac0a197d07b995c65c94e
wpt-pr: 23954
Automatic update from web-platform-tests
Add experimental feature for out-of-blink CSP Embedded Enforcement
Content Security Policy Embedded
Enforcement (https://w3c.github.io/webappsec-cspee/), a mechanism
which checks whether a frame is allowed to be embedded, is currently
being checked in blink. We want to start an experiment to port this
check to the browser, alongside with other frame embeddedding checkers
like frame-ancestor.
This change adds an experimental feature which disables the current
checker together with a virtual test suite for that feature. The
actual implementation of oob-CSPEE will come in later steps.
Change-Id: Ie54d2cf64ac4ad87202d4825b01dbdcec214e332
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215333
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774988}
--
wpt-commits: 883bf1307adddfce5b315fdf5f8c4e45f3b83e5b
wpt-pr: 23818
Automatic update from web-platform-tests
[scroll-animations] Add animation-timeline property behind flag
This CL adds parser/ComputedStyle support for the animation-timeline
property. The property doesn't have any affect yet.
The property accepts auto, none, <custom-ident> or <string>, and
(currently) needs to remember how it was specified in order to
serialize correctly. This is a situation that is useful in other
scenarios as well (e.g. animation-name), and it's a pattern I expect
to see more of in the future, hence this CL adds the 'StyleName' and
'StyleNameOrKeyword' classes for this purpose.
Note that expanding animation-timeline from the animation shorthand
is not possible yet, and will be done in a separate CL.
Bug: 1074052
Change-Id: Ie37e520fd64e9556863c09d97d8c9f8f7c5f7fbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223950
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774902}
--
wpt-commits: 39af2cfd9c6b0997f799a2dc01c5896664259ee0
wpt-pr: 23913
Automatic update from web-platform-tests
[@property] Remove CSSRule.PROPERTY_RULE
The practice of defining constants on CSSRule is now deprecated [1],
hence we decided to not introduce CSSRule.PROPERTY_RULE after all [2].
For @property rules, CSSRule.type is now supposed to return zero [3],
which requires adjustment to all previous call sites of CSSRule::type(),
since that function will no longer be usable to differentiate between
different CSSRule subclasses (which is still needed internally).
This CL therefore adds the GetType function, which returns
the non-zeroed type.
Note: I wanted to make CSSRule::Type an enum class to ensure that
I didn't miss any calls to CSSRule::type(), but the bindings code
is unfortunately generating static_asserts that requires CSSRule::Type
to remain a regular enum.
[1] https://wiki.csswg.org/spec/cssom-constants
[2] https://github.com/w3c/css-houdini-drafts/issues/991
[3] https://drafts.csswg.org/cssom/#dom-cssrule-type
Bug: 973830
Change-Id: If8713b322166c432070365b1dc1f134b82ed87d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224259
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774872}
--
wpt-commits: df6a748a3e995e32930d8f29761361fe6740d48e
wpt-pr: 23910
Automatic update from web-platform-tests
Repaint remote frames when new layer is set
Remote frames in CAP can end up incorrectly sized 0,0 on initial render
which makes the iframes content not show up. The initial
RenderFrameProxy::SynchronizeVisualProperties can come in before the
RemoteFrameView has updated its compositing rect, which leaves the
created SurfaceLayer with a 0,0 size.
The RemoteFrameView compositing rect is only updated after Paint in the
document lifecycle (see LocalFrameView::UpdateLifecyclePhasesInternal)
and RenderFrameProxy::SynchronizeVisualProperties is called during
intersection observer steps (also after paint). Since the synchronized
properties have changed, a new SurfaceLayer is created at the correct
size. When setting this SurfaceLayer on RemoteFrame, the existing
invalidation of SetNeedsCompositingUpdate is not sufficient in CAP to
have a new frame generated with the updated layer.
In pre-CAP, this is not an issue - the oopif content appears with the
first frame produced due to the ContentsLayer size update via
CompositedLayerMapping::UpdateContentsRect in the compositing phase of
the document lifecycle.
To fix this for CAP, we add a SetNeedsPaint on the frame owner
element's paint layer, and schedule another frame to ensure this gets
picked up, since these updates typically will come in outside of the
document lifecycle.
R=pdr@chromium.org
Bug: 1078255
Change-Id: I7333a79b3cfbca303fe388bea6d7df176b0e1f41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227897
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Daniel Libby <dlibby@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#774868}
--
wpt-commits: 76f41a5c24c36011c5251dd96694342381231a2c
wpt-pr: 23930
Automatic update from web-platform-tests
Iterate sorted keys when comparing keyframes for testing
Since enumeration does not guarantee any specific order, we can get
test failures when the order changes for an unrelated reason
(typically when adding a new CSS property).
Fix by sorting the keys before comparing, which ensures that we fail
the same way every time.
Change-Id: I7bbc8e98bc17120084c6934d71f092ee0ba016da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2228724
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774670}
--
wpt-commits: 5c06da35ce8006aec00019449edbe352fa8bc593
wpt-pr: 23946
Automatic update from web-platform-tests
[NativeFS] Change getSystemDirectory to getOriginPrivateDirectory.
In https://github.com/WICG/native-file-system/pull/174 the spec
for how sandboxed FS is exposed was change, this updates to
implementation to match the spec.
R=mek@chromium.org
Bug: 1081287
Change-Id: I0e381c873db98e30baed6679be048031b385cc50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220685
Commit-Queue: Hazim Mohamed <hazimmohamed@google.com>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774745}
--
wpt-commits: 1e1431774d766756367132d3c976aeaf8998a8d0
wpt-pr: 23844
Automatic update from web-platform-tests
[COOP access reporting] Preliminary WPT tests.
Add some basic WPT tests about the COOP access reporting feature.
No web browsers actually implement this. As a result, chrome do not
pass them yet.
The tests aren't complete yet, they will evolve along the specification
and the implementations.
Bug: 922191
Change-Id: I9aa03e727252086eb64c0110afc9b5885b66802d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225757
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774599}
--
wpt-commits: cbb4b64833f40c8089ba67d4fe807ffba603e6b5
wpt-pr: 23909
Automatic update from web-platform-tests
Mark some idlharness.html tests as timeout=long
These are symptomatic of crbug.com/1047818, but to stop the pain for
sheriffs lets mark them timeout=long for now.
TBR=lpz@chromium.org
Bug: 1090455, 1090484
Change-Id: I67b37d6ad915b28d57a95be88243eed619585b7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2229058
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Luke Z <lpz@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774614}
--
wpt-commits: 596273ec31202ee54c44bf5b2f1be35ef53d1f8f
wpt-pr: 23945
Automatic update from web-platform-tests
Add a test for dynamic modification of the content of an mtable (#23942)
* Add a test for dynamic modification of the content of an mtable
https://github.com/mathml-refresh/mathml/issues/57
* add help
--
wpt-commits: 8224cbf867f8eb1da7d2bb04267e8062a9144794
wpt-pr: 23942
Automatic update from web-platform-tests
Workers: test where Worker/SharedWorker are exposed
And remove broken tests.
For https://github.com/whatwg/html/pull/5601.
--
wpt-commits: 84d101a169cf21f345a5c3bd39f27b919a16195b
wpt-pr: 23381
Automatic update from web-platform-tests
Correct form of error returned for RTCError
Bug: chromium:1030631
Change-Id: Idc0b9fe6d4c4db05741cd477ad25f98f83b554e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2196165
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774551}
--
wpt-commits: 86610ed7689fe7df37624a8ff1569e4d67422a81
wpt-pr: 23935
Automatic update from web-platform-tests
Add dynamic tests for MathML elements using mrow or mtext layout. (#23939)
https://github.com/mathml-refresh/mathml/issues/57
--
wpt-commits: 29982ce8a41c362213fd149c3bdf01b2e45f35e6
wpt-pr: 23939
Automatic update from web-platform-tests
Add dynamic test for id and style attributes on MathML elements (#23936)
https://github.com/mathml-refresh/mathml/issues/57
--
wpt-commits: e8a0852fa44996c2b24d02c3b8fb35e8110ac5af
wpt-pr: 23936
Automatic update from web-platform-tests
Add a wpt build-docs command
This makes it obvious how to do that and avoids worrying about
virtualenvs and installing sphinx
--
wpt-commits: a43cfa2dd30697c5c75e3581547551773af146d9
wpt-pr: 23922
