Automatic update from web-platform-tests[Azure Pipelines] Document "Build pull requests from forks of this repository" (#13952)
--
wpt-commits: e0e8196c242c8fb1d2a62c13f23455a9d03bd4bb
wpt-pr: 13952
Automatic update from web-platform-tests[filter-effects] Parsing of backdrop-filter (#13871)
Test parsing, serialization and computed value for backdrop-filter
https://drafts.fxtf.org/filter-effects-2/#BackdropFilterProperty
--
wpt-commits: 208508bfdb7a8a9692394488bec2237102e16962
wpt-pr: 13871
Automatic update from web-platform-tests[LayoutNG] Fix vertical-align: text-top in quirks mode
When in quirks mode and there are no text siblings; e.g.:
<div><img><span>text</span></div>
and 'vertical-align: text-top' applied to <img> hits
DCHECK failure and results in incorrect position.
The test ensures that results are the same with the standard
mode.
Bug: 901123
Change-Id: I30564c66d5847f09caf3672ba3d456c0eb798d3e
Reviewed-on: https://chromium-review.googlesource.com/c/1320529
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605965}
--
wpt-commits: 48c278aad9f1570f14e47472e7cf304865602192
wpt-pr: 13962
Automatic update from web-platform-testsfix video reference in webvtt rendering tests
--
wpt-commits: c94bfaa0f97be784245d5c5405ebf2cae78df2f7
wpt-pr: 13553
Automatic update from web-platform-testsFix RTCRtpTransceiver direction tests (#13914)
* Update RTCRtpTransceiver setDirection to direction setter
* Fix currentDirection in RTCRtpTransceiver-direction.html
* Add negative test for setDirection
--
wpt-commits: d37a815dbca209eafc8eb71cb59ce59f4e66f975
wpt-pr: 13914
Automatic update from web-platform-testsRemove support for supportedTypes in Payment Request (#13858)
--
wpt-commits: 615bb572c95add74ca4fb9fed4af5269a49cf4ef
wpt-pr: 13858
Automatic update from web-platform-testsAdded mechanisms for default policy
With a default policy defined, assignments implicitly call createXXX on the default policy
Added ScriptState* to the accessors visible from JavaScript
Tests were updated to check string assignment when trusted-types are needed before and after the default policy is defined
Bug: 739170
Change-Id: I9bb841d69f324b841602d41abd71f753a9858af8
Reviewed-on: https://chromium-review.googlesource.com/c/1207530
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605720}
--
wpt-commits: 24373750793a107c28dbfde50d61cfae192fb485
wpt-pr: 12952
Automatic update from web-platform-testsRun py36-flake8 also for tools/wpt/ (#13947)
--
wpt-commits: bfc7ce508b754e84e95830c2186f1fa8eb9f179e
wpt-pr: 13947
Automatic update from web-platform-testsRevert "Make XR FrameData and Environment mojo associated"
This reverts commit 126a1168e3bcffb43c706822b3aa28695840310f.
Reason for revert: Broke compile: https://logs.chromium.org/logs/chromium/bb/chromium.chrome/Google_Chrome_Win/39908/+/recipes/steps/compile/0/stdout
Original change's description:
> Make XR FrameData and Environment mojo associated
>
> The XRFrameDataProvider now returns an associated
> XREnvironmentDataProvider interface so that the
> two share callback queues and thus allow strict
> ordering of the two interfaces. This is critical
> for frame synchronization between frames and the
> associated environment data.
>
> Note: We can't just mark the interfaceptrs for
> XRFrameDataProvider and
> XREnvironmentIntegrationProvider as associated
> in the XRSession struct. XRDevice implementations
> mostly live on separate threads from the
> XRFrameDataProviders, so we'd have extra thread
> hopping. For the VR headsets we explicitly live
> off the main thread to avoid latency, and because
> we do some work that may block the thread the
> XRFrameDataProvider lives on (for example waiting
> for vsync, or submitting frames to headset APIs).
>
> Bug: 867057, 876135, 843376
> Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
> Reviewed-on: https://chromium-review.googlesource.com/c/1171794
> Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Bill Orr <billorr@chromium.org>
> Reviewed-by: Klaus Weidner <klausw@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605545}
TBR=dcheng@chromium.org,klausw@chromium.org,billorr@chromium.org,lincolnfrog@chromium.org
Change-Id: I7a2408629460f456bf1189acdb0837f7d22a7919
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 867057, 876135, 843376
Reviewed-on: https://chromium-review.googlesource.com/c/1318805
Reviewed-by: Dmitry Titov <dimich@chromium.org>
Commit-Queue: Dmitry Titov <dimich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605551}
--
Merge pull request #13939 from web-platform-tests/chromium-export-0ef86cd598
Revert "Make XR FrameData and Environment mojo associated"
--
wpt-commits: 97ef8fa350d0b1cf5c4692a71b1040d66266e7b7, b306f085d1a008b7636b60efa67a5b89d1fc2f52
wpt-pr: 13939
Automatic update from web-platform-testsFix and re-enable simplecall-no-ssrcs.https.html.
With the changes, the test should pass regardless of if the Chrome or
Firefox behavior is used for what to do when no MSIDs are signaled.
Follow-up work is needed to test both the case of "a=msid:-" and no
"a=msid" line whatsoever, awaiting spec issue to be resolved:
https://github.com/w3c/webrtc-pc/issues/2027
// Relying on fippo's approval to land.
TBR=hta@chromium.org
Bug: 901711
Change-Id: Icaf089d206413510aadad54a0c10b2674450385a
Reviewed-on: https://chromium-review.googlesource.com/c/1319612
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605678}
--
wpt-commits: bce2269d0f17d2a89247895cbee21530ae83c96e
wpt-pr: 13950
Automatic update from web-platform-tests[presentation-api] Revise the test for reconnecting multiple presentations (#13196)
Test closing and reconnecting to multiple connections simultaneously
--
wpt-commits: 7a51b509430cc115df632608356999fa18ac4491
wpt-pr: 13196
Automatic update from web-platform-testswebrtc: rename DTLSTransport.transport to .iceTransport (#13915)
test for https://github.com/w3c/webrtc-pc/pull/2017
--
wpt-commits: c05700b258089fd547808c54707cdc3a64b48344
wpt-pr: 13915
Automatic update from web-platform-testsRemove the "W3C WebSocket API" prefix from websockets/ tests (#13478)
This prefix doesn't add any useful information, and isn't used in all
tests in this directory. Noticed because of the screen real estate it
takes up in a view like this:
https://wpt.fyi/results/websockets/Send-binary-65K-arraybuffer.any.html
In the directory, this command was run, on macOS:
git grep -lF 'W3C WebSocket API - ' | xargs sed -i '' 's/W3C WebSocket API - //g'
--
wpt-commits: 1e747acc90ecdbd23ef3348a144b77696cced55b
wpt-pr: 13478
Automatic update from web-platform-testsUpdate RTCPeerConnection-setRemoteDescription-tracks.https.html as MediaStream has no constraint on the order of the track (#13940)
--
wpt-commits: 89c900d2e2bae0592564dfc5bf06cc4b08b3cac5
wpt-pr: 13940
Automatic update from web-platform-tests[wptrunner] Convert data prior to transmission
A recent improvement to wptrunner modified the way data structures are
transmitted from the browser to the WebDriver server [1]. One
consequence of this change is that the data structures are created in a
JavaScript realm which differs from the realm in which the "Execute
Script" WebDriver command is running. As of version 17, Microsoft Edge
does not correctly serialize cross-realm values, so referenced
improvement unintentionally precluded testing in that browser.
Serialize and deserialize the results data structure from the realm of
the WebDriver command to avoid this problem.
[1] https://github.com/web-platform-tests/wpt/pull/13419
--
wpt-commits: e3738ec2754f0c3fb44a03af3104db1decf9fca7
wpt-pr: 13938
Automatic update from web-platform-testsXMLHttpRequest: manipulate Content-Type a little more
99f4fdcd906411c036e96c055e28b3e6ca84a1cc was not entirely correct unfortunately.
--
wpt-commits: 47aa8753bba8656899eca2e7c3851a7c75c1d2d7
wpt-pr: 13920
Automatic update from web-platform-testsChange the button type to int in the pointerActionSequence API
In order to match with test_driver Actions API, we need to change the
button type from string to int in the pointerActionSequence API and the
related web platform tests and layout tests.
Bug: 893480
Change-Id: I151849d31038cf40a2a603196e0f616e15d89072
Reviewed-on: https://chromium-review.googlesource.com/c/1297637
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605605}
--
wpt-commits: 41f76e27e00de380d5a100aa0c1065fa202e9c0a
wpt-pr: 13933
Automatic update from web-platform-testsMake XR FrameData and Environment mojo associated
The XRFrameDataProvider now returns an associated
XREnvironmentDataProvider interface so that the
two share callback queues and thus allow strict
ordering of the two interfaces. This is critical
for frame synchronization between frames and the
associated environment data.
Note: We can't just mark the interfaceptrs for
XRFrameDataProvider and
XREnvironmentIntegrationProvider as associated
in the XRSession struct. XRDevice implementations
mostly live on separate threads from the
XRFrameDataProviders, so we'd have extra thread
hopping. For the VR headsets we explicitly live
off the main thread to avoid latency, and because
we do some work that may block the thread the
XRFrameDataProvider lives on (for example waiting
for vsync, or submitting frames to headset APIs).
Bug: 867057, 876135, 843376
Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
Reviewed-on: https://chromium-review.googlesource.com/c/1171794
Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605545}
--
wpt-commits: 2ba8053bfa3946457355fa73d2873144fe4479d2
wpt-pr: 13764
Automatic update from web-platform-testsCope even better with the mess we leave behind after a continuation.
Tried to fix this in https://chromium-review.googlesource.com/c/1309777
but incorrectly assumed that bogus continuation chains were formed by
direct siblings. But they may also be arbitrary-level cousins. Need to
walk through all non-atomic inlines between one continuation object and
the next in the chain, to figure out whether there is an anonymous block
between two objects in the continuation chain. Only then should we
update the positionedness of anonymous blocks. Only perform this check
if positionedness changed, since it's not for free.
Bug: 901598
Change-Id: I3e49a4ce8081a4a3190cc1569480189cbcccdcc4
Reviewed-on: https://chromium-review.googlesource.com/c/1317627
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605465}
--
wpt-commits: fb4466fa28e359a770f6d7007a2a1302fec0c8a2
wpt-pr: 13919
Automatic update from web-platform-testsCorrect inherited feature policy when allow attribute is used.
This fixes an error in the inherited policy calculation where a frame
which was explicitly allowed to use a feature through the Feature-Policy
header would be blocked if the "allow" attribute was also present on
the iframe element.
The behaviour now matches the spec algorithm at
https://wicg.github.io/feature-policy/#define-inherited-policy-in-container
Tests have been added to catch this case.
Change-Id: I7a394202c615be3088fda738d7fc65f16bcadf34
Reviewed-on: https://chromium-review.googlesource.com/c/1293610
Reviewed-by: Luna Lu <loonybear@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605431}
--
wpt-commits: d5f4dec283def0baeca6e5a88223dac67935e798
wpt-pr: 13717
Automatic update from web-platform-testsCSS: serialize pointer-events keywords in lower case
https://drafts.csswg.org/cssom/#serializing-css-values
"To serialize a CSS component value depends on the component, as follows:
keyword
The keyword converted to ASCII lowercase."
Bug: 901666
Change-Id: Iff579a363de13441c75bbebfc951095b071f6060
Reviewed-on: https://chromium-review.googlesource.com/c/1317300
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605383}
--
wpt-commits: f917e2dfc6649f9217f51dec9fd45eaef16188fc
wpt-pr: 13917
Geoffrey Sneddon
Philip Jägenstedt
moz-wptsync-bot
Eric Willigers
Hiroki Nakagawa
Koji Ishii
Gary Katsevman
Youenn Fablet
Charles Vazac
Mark Roberts
Marcos Cáceres
Jan-Ivar Bruaroey
Daniel Vogelheim
Dmitry Titov
Henrik Boström
Tomoyuki Shimizu
Philipp Hancke
youennf
Mike Pennisi
autofoolip
Anne van Kesteren
Christian Bromann
Lan Wei
Francois Remy
Max Rebuschatis
Emircan Uysaler
Morten Stenshorne
Ian Clelland
Zhuoyu Qian