Automatic update from web-platform-tests
Consolidate xrWebGLLayer_framebuffer tests
xrWebGLLayer_framebuffer was a recently added test that both duplicated
and was at odds with parts of xrWebGLLayer_opaque_framebuffer. This
change deletes xrWebGLLayer_framebuffer and ports the new requirements
from that file that are spec compliant to the opaque_framebuffer file.
Bug: 986672
Change-Id: I0f649297f2d4f93f2d17cb396185436e7cb7c6bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727329
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@{#682477}
--
wpt-commits: 446fbc1f462dce21ac22e4f6e8e2ca3ebb60c31a
wpt-pr: 18183
Automatic update from web-platform-tests
Revert "location.hash = '' should always result in an empty fragment, not no-fragment"
This reverts commit fb0f9e392b20395b45fe3aa7bcaaae3bdb8faf5d.
Reason for revert: breaks rendering on https://svelte.dev/tutorial/basics
Original change's description:
> location.hash = '' should always result in an empty fragment, not no-fragment
>
> So far in |setHash|, old fragment identifier and new fragment identifier are
> compared ignoring nullity.
>
> When fragment has never been set, |old_fragment_identifier| is null.
> In this situation, |location.hash = ''| is called,
> |new_fragment_identifier| is not null empty value.
> |EqualIgnoringNullity| treats these as the same, |setHash| does nothing.
>
> So, this patch compare old and new fragment by == operator
> not |EqualIgnoringNullity|.
>
> Bug: 615300
> Change-Id: Id509bc5066eeee83236ecb4ee816ecb90540a260
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647298
> Commit-Queue: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#670795}
TBR=dcheng@chromium.org,japhet@chromium.org,bluewhale.marc@gmail.com
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 615300
Change-Id: I6e47d0d1711b197c6e8e35af7dc43e67a6cb4ebb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726953
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682440}
--
wpt-commits: a295f696f9e4eb0e6e9475e132a8d7a9855bbacf
wpt-pr: 18175
Automatic update from web-platform-tests
[cleanup] Remove Node param from CSSValueFromComputedStyle.
A cleanup of the cleanup! Upon further inspection the node parameter
isn't strictly needed anymore.
This has one slight behaviour change, which I think was incorrect:
flexItem.computedStyleMap().get('min-height') == 0px now.
This is more correct I believe as computedStyleMap should act as if a
box isn't attached, which is the same behaviour if elem wasn't attached
to the document.
Change-Id: I4522d1f591cdfe7ec88522f6da49be599d2db4ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716089
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682423}
--
wpt-commits: b4ce804de436211deeb37dbd9130634c3a47a94e
wpt-pr: 18161
Automatic update from web-platform-tests
Sort tracks by id in MediaStreamAudioSourceNode
When there are multiple tracks in a MediaStreamAudioSourceNode, the
track to use is the first track after sorting the tracks based on a
lexicographic ordering of the track ids using code unit values.
Feature: https://www.chromestatus.com/feature/5749997033226240
Bug: 984994, 983790
Change-Id: I0c194caa98de1f0283927dc0206219ab7679c86d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1706775
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#681066}
--
wpt-commits: fcf3d9f2a2927fe4b9d01cafb07bf849df52e11e
wpt-pr: 17891
Automatic update from web-platform-tests
Do not throw errors in copyFromChannel/copyToChannel
If the buffer offset lies outside the boundaries of the AudioBuffer , silently
do nothing instead of throwing an error.
This is a change in behavior where we used to throw an error if the offset was greater
than or equal to the size of the AudioBuffer.
Spec issue: https://github.com/WebAudio/web-audio-api/issues/1884
Bug: 987295
Change-Id: I61955108af0fa3072a2c7174889827781c06747e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717185
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682321}
--
wpt-commits: 28d7981ed812d2993d2b6e6584578d6f9fc7b55c
wpt-pr: 18155
Automatic update from web-platform-tests
[LayoutNG] Fix placing floats within zero available space.
There was special logic added for zero width inlines in:
https://chromium-review.googlesource.com/c/chromium/src/+/870950/
This logic allowed for zero-width layout opportunities beside floats for
inline-level content.
This also added a TODO saying this was probably wrong for floats.
.... it turned out this was wrong for floats. :)
This adds a flag to switch between these two behaviours.
Bug: 988505
Change-Id: I2db5e0b9cb6f90cb131821ad205728289d9098ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725309
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682265}
--
wpt-commits: 179f0011944fe49e83669ef7931605a1bbf827ef
wpt-pr: 18158
Automatic update from web-platform-tests
MathML: Add test to verify that new math layout ignore width/height (#18171)
* MathML: Add test to verify that new math layout ignore width/height
See https://github.com/mathml-refresh/mathml/issues/45
--
wpt-commits: 73a80e4008e7757e46ecb68f64797e9499ec5892
wpt-pr: 18171
--HG--
rename : testing/web-platform/tests/mathml/relations/css-styling/padding-border-margin/helper.js => testing/web-platform/tests/mathml/support/box-comparison.js
Automatic update from web-platform-tests
Make MathML padding/margin/border-002 tests stricter. (#18166)
Currently, these tests only verify the metric changes on the parent.
This commit makes the tests stricter by checking that the size changes are
actually applied to the element itself (padding/border) or not (margin).
--
wpt-commits: cac06f892411e85fc4b478a078b38f478c1c850a
wpt-pr: 18166
Automatic update from web-platform-tests
MathML: Add tests for margin/padding/border in RTL mode. (#18164)
Additionally, this also:
- remove duplicate "left" property in padding-border-margin-001
- add feature detection for padding/border/margin-001 since they rely on mspace
and now the dir attribute.
--
wpt-commits: 699ce5fdb8ad9ad381fa03c7b2d219ba3bc5c597
wpt-pr: 18164
Automatic update from web-platform-tests
Service worker update check handles 404 imported scripts appropriately
Previously 404 was just treated as a identical scripts, but it's wrong because
if a new worker tries to import the script during the initial script evaluation
for a update, it should fail due to the network error. This CL adds code to
capture the network failure in ServiceWorkerSingleScriptUpdateChecker and
replay the network failure in ServiceWorkerNewScriptLoader.
The failure in update-import-scripts.https.html will be fixed once
ServiceWorkerImprotedScriptUpdateCheck is enabled.
Bug: 648295
Change-Id: Ibcd879cc4c46b9878b1f6df1a6983c110f606fe7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715414
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Auto-Submit: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682189}
--
wpt-commits: e5d044d1d420973cd707ec7832e664e0e3d1fd6c
wpt-pr: 18160
Automatic update from web-platform-tests
MathML: make some padding/margin/border tests stricter. (#18146)
This checks that padding/border values are included in the mrow size but
margin values are not.
--
wpt-commits: f95d940581f2044f930ba4061ce9450bed74f676
wpt-pr: 18146
Automatic update from web-platform-tests
MathML: Fix expectation for attribute mappings on mi and merror. (#18163)
mi and merror have default CSS rules in the UA stylesheet for text-transform,
color and background.
--
wpt-commits: 0b5df94048c3a31adbc5cefa7d4ed1103da95e58
wpt-pr: 18163
Automatic update from web-platform-tests
LazyLoad: Add test for deferred images using attributes at parse time
This CL adds tests for base URL, referrer-policy and crossorigin state
at parse time are retained when the deferred frame is loaded-in.
Bug: 984983
Change-Id: Ifab76a15a4addf750251cbfd0e6849c535b95531
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1719445
Commit-Queue: rajendrant <rajendrant@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682123}
--
wpt-commits: f5d30dadbd7f158898c64aa6fdb1cd843f54fd1d
wpt-pr: 18087
Automatic update from web-platform-tests
Remove XRWebGLLayer.context attribute
It was removed from the latest version of the WebXR spec.
Bug: 987026
Change-Id: I44186ad46827dee8227e07b9f5039ff3ee5217aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721048
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682062}
--
wpt-commits: 9cefb45585f175f4bf663e1069f0fb14b5237ef5
wpt-pr: 18120
Automatic update from web-platform-tests
Remove XRDeviceImpl
The WebXR API used to have an intermediate device that must be obtained
prior to requesting sessions. This device was removed from the API.
This change removes the implementation backing it (across a mojo
boundary) in the browser process.
Effectively this change merges XRDeviceImpl and VRServiceImpl and
simplifies some parts of the code related where multiple async
operations were required.
Bug: 944987
Change-Id: If1c426baab8e3149059f32773e9a21313769df0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1676344
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682057}
--
wpt-commits: 76d99090df4409748a5eb44dfaa91f9bddf8f7da
wpt-pr: 17632
Automatic update from web-platform-tests
Set WebXR Gamepad.index to -1
Bug: 974058
Change-Id: I7330d1d79df05f040956e920757074d8135387f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721037
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682017}
--
wpt-commits: 620a86bfcceb548cf0ddb7e1c528e8edb89c6226
wpt-pr: 18118
Automatic update from web-platform-tests
Remove XRLayer
Now, only XRWebGLLayer is defined by the spec and it does not inherit
from XRLayer.
Bug: 987023
Change-Id: Iaf4f878b33ef816df1e85a39642dea25f318bfa3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721929
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Cr-Commit-Position: refs/heads/master@{#681905}
--
wpt-commits: cd3b99a919f2d8119d94c21de51dbbda315f408f
wpt-pr: 18119
Automatic update from web-platform-tests
[wptserve] Validate alternate_host configuration (#17943)
Some values of `alternate_host` will invalidate tests. Script the server
to refuse to run if the operator supplies an inappropriate value.
--
wpt-commits: b683b48465900b5585bf08ee4b6c25b219944333
wpt-pr: 17943
Automatic update from web-platform-tests
MathML: Add tests to check legacy mathsize values (#18037)
These values have been removed from MathML Core ( https://github.com/mathml-refresh/mathml/issues/7 )
--
wpt-commits: 54f7b9af46a8a8b6e9d43907d19d3250cbfbc83e
wpt-pr: 18037
Automatic update from web-platform-tests
MathML: remove msqrt test from direction-overall.html (#18156)
This test is no longer valid now that dir is supported in the msqrt element.
The child positions are already tested in writing-mode-002.html.
--
wpt-commits: 8f4701ee191bd368f440a310a095672f6cae7ca2
wpt-pr: 18156
Automatic update from web-platform-tests
MathML: Add generic tests for layout in various writing modes. (#18143)
* MathML: Add generic tests for layout in various writing modes.
This relies on the basic templates from mathml-fragments to cover at least
all MathML elements, but more advanced cases might be added later.
Additional changes:
- mathml/support/mathml-fragments.js: msub, msup and msubsup cannot contain
arbitrary children so remove the mathml-container tag.
- mathml/support/layout-comparison.js: check that the children of element and
reference have the same display values and skip those that have
"display: none" since they are not laid out.
--
wpt-commits: a972fe4b170e31107a3429299de738af881a53e2
wpt-pr: 18143
Automatic update from web-platform-tests
Add test to check visual rendering of padding/border/margin on the mrow element. (#18145)
--
wpt-commits: 1c97ca89d6d15b38fd66842d7d23f321f7ade664
wpt-pr: 18145
