Automatic update from web-platform-testsFix #11454: Set --verify-log-full to False for ci/check_stability.py (#11464)
I'm not entirely sure why #10988 made this default to on, given that
was a change of behaviour from before, so let's turn it back off
given it's causing breakage, as documented in #11454.
--
wpt-commits: 33280b704b880ca34ed976e9097a854697079640
wpt-pr: 11464
Automatic update from web-platform-testsFix test flakiness around multi-threaded blob URL revocation.
Registering a new blob URL in the worker will ensure (at least in chrome)
that the revocation has been fully processed before the main thread
tries to fetch the now revoked URL.
Bug: 851942
Change-Id: I12e794682dbb5b34dc08fe2a7d398e3ba02aaffa
Reviewed-on: https://chromium-review.googlesource.com/1097230
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566460}
--
wpt-commits: 98530fb94412077886e8df96e25bfdcd3ce460d3
wpt-pr: 11477
Automatic update from web-platform-testsRemove array destructuring for WebDriver execute async script tests
IE does not support array destructuring in a `let` statement. This commit
allows the execute_async_script tests for collections to run on IE 11.
--
wpt-commits: c81e3488e59040bb218fcd56ca00e7fe802534c4
wpt-pr: 11475
Automatic update from web-platform-testsFix errors in external/wpt/RTCDTMFSender-insertDTMF.https.html.
This is in preparation for RTCRtpTransceiver/Unified Plan support.
Updated tests:
insertDTMF() should throw InvalidStateError if
transceiver.currentDirection is [recvonly/inactive]
Just like the tests fixed in
https://chromium-review.googlesource.com/c/chromium/src/+/1095275, the
tests were not set up properly.
Fixed the tests so that currentDirection is what it is supposed to be
according to the test description. Also updated the tests to use
async/await.
These tests will pass when we support RTCRtpTransceiver (WIP CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1025771).
Bug: 777617
Change-Id: I59eab4e4a15bb82e2dabe68d56f6d55b0e380e75
Reviewed-on: https://chromium-review.googlesource.com/1097083
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566432}
--
wpt-commits: 692f3f487851b8617822517451f6a557b3b3171f
wpt-pr: 11472
Automatic update from web-platform-tests[css-grid] Content Alignment as part of the track sizing algorithm
The CSS WG resolved [1] that Content Alignment should account to the
track sizing algorithm.
The sizing algorithm has been modified so that two new steps (1.5
and 2.5) were added to compute the Content Alignment offsets after
resolving the columns' and rows' sizes respectively.
This change decouples the Content Alignment logic from the tracks
position, so that we can use it as part of the track sizing algorithm.
I also had to store the whole ContentAlignmentData structure in two
class attributes. We need both, position and distribution offsets, to
be used in different parts of the layout logic.
Finally, since the ContentAlignmentData is now used as persistent
memory, we had to remove the STACK_ALLOCATED flag; hence, I think
using DISALLOW_COPY_AND_ASSIGN and let the functions update the
structure's internal field is a more efficient approach to commit
this change.
[1] https://github.com/w3c/csswg-drafts/issues/2557
Added WPT
* grid-content-distribution-must-account-for-track-sizing-001.html
* grid-content-distribution-must-account-for-track-sizing-002.html
Bug: 844744
Change-Id: I90019a96b148d3713467e35fde9482d0d39b1ced
Reviewed-on: https://chromium-review.googlesource.com/1067918
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#566412}
--
wpt-commits: 73ed379a1437407749c730239019bd61528b060b
wpt-pr: 11115
Automatic update from web-platform-testsClean up FileAPI idlharness tests
After fixing #10338, we can leverage add_dependency_idls to import the 'real' untested idl from sources cleanly.
--
wpt-commits: ce580dab49d64f723453cf56c2c501bb54beb7bc
wpt-pr: 11441
Automatic update from web-platform-testscustom-elements: Element created by createElementNS(ns, qname, options) with valid custom element name and undefined options should be upgraded immediately
createElementNS(XHTML_NS, 'my-element', undefined) was not being
upgraded immediatedly, though both createElementNS(XHTML_NS,
'my-element') and createElementNS(XHTML_NS, 'my-element', {}) were.
Bug: 841725
Change-Id: Iccc4f0e98b1de65288381dd9ac106e71bfc5d0c8
Reviewed-on: https://chromium-review.googlesource.com/1096812
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566374}
--
wpt-commits: 05c1a1fb132cc0e37f49c8eb1a5df096098f35be
wpt-pr: 11470
Automatic update from web-platform-testsFix errors external/wpt/RTCPeerConnection-removeTrack.https.html.
This is in preparation for RTCRtpTransceiver/Unified Plan support.
"Calling removeTrack with valid sender should set sender.track to null"
Asserting that direction changes from 'sendrecv' to 'recvonly', this
is explicit in the spec[1].
"Calling removeTrack with currentDirection blah should set direction to
blah"
The tests that meant to set up currentDirection to be 'sendrecv' or
'recvonly' before removeTrack() were incorrect. Tests updated to set
up currentDirection correctly. Also updated them to use async/await
because that's much nicer.
These all fail because we don't have transceivers yet, but when running
these changes in the RTCRtpTransceiver WIP CL[2], they all pass.
[1] See step 10 of
https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-removetrack
[2] https://chromium-review.googlesource.com/c/chromium/src/+/1025771/
Bug: 777617
Change-Id: Ie3c077d14ea30038a06a98ecbeea475ac824dd9c
Reviewed-on: https://chromium-review.googlesource.com/1095275
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566366}
--
wpt-commits: ae0eec132996427a8189b9928791499e2faf4d81
wpt-pr: 11459
Automatic update from web-platform-testsMerge pull request #11335 from frivoal/git-doc-lint
Mention the lint tool in the github tutorial
--
wpt-commits: ed8650a5dbbaacd706dd99e24b0cacaadaef74e2
wpt-pr: 11335
Automatic update from web-platform-tests[css-contain] Size containment should ignore contents in flexbox/grid
The spec is pretty clear
(https://drafts.csswg.org/css-contain/#containment-size):
"1. When laying out the containing element,
it must be treated as having no contents."
The patch modifies ComputeIntrinsicLogicalWidths() and
FirstLineBoxBaseline() in LayoutFlexibleBox and LayoutGrid,
so the contents are ignored if the flex or grid container
has "contain: size".
Buttons are implemented as flexboxes internally,
so they get fixed too thanks to this change.
BUG=850169
TEST=external/wpt/css/css-contain/contain-size-button-001.html
TEST=external/wpt/css/css-contain/contain-size-flexbox-001.html
TEST=external/wpt/css/css-contain/contain-size-grid-001.html
Change-Id: Ia08c2c7b31126911cb4f0d1fc70aa444c22af8e3
Reviewed-on: https://chromium-review.googlesource.com/1093854
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566228}
--
wpt-commits: af6293eecd7db39b8f696be1b051f329db7cc87f
wpt-pr: 11446
Automatic update from web-platform-testsAdjust test thresholds for win10
These tests fail on Windows 10 because the error thresholds are a bit
too tight. Relax them a bit so that these pass on my Win10 machine.
Bug: 851605
Change-Id: Ie7795205550a43928e7f0963e4411264e3ded37b
Reviewed-on: https://chromium-review.googlesource.com/1095859
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566181}
--
wpt-commits: be959408023fe02cf79abe70f6018598a7004a88
wpt-pr: 11467
Automatic update from web-platform-tests[testharness.js] Extend test suite with "variants"
Feature description (from modification to `README.md` file):
> `testharness.js` is expected to function consistently in a number of
> distinct environments. In order to verify this expectation, each functional
> test may be executed under a number of distinct conditions. These conditions
> are applied using WPT's "test variants" pattern. The available variants are
> defined in the `variants.js` file; this file must be included before
> `testharness.js`. Every test must specify at least one variant.
Extend test harness for `testharness.js` with additional validation to
ensure that each test is correctly formatted. Introduce a minimal UI to
help future contributors discover this new functionality and its
motivation.
--
wpt-commits: 08995880734011eed359c4e79420db29626016ff
wpt-pr: 11150
Automatic update from web-platform-tests[sensors] Check that sensor frame and focused frame of same origin
In order to implement mitigation stragegy defined in [1], focused
frame and frame associated with the sensor should be of the same
origin.
[1] https://www.w3.org/TR/generic-sensor/#focused-area
Bug: 849501
Change-Id: I06fce4e66873cd98e59e45d00ffe27de8e7d66f9
Reviewed-on: https://chromium-review.googlesource.com/1087049
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Alexander Shalamov <alexander.shalamov@intel.com>
Cr-Commit-Position: refs/heads/master@{#566096}
--
wpt-commits: 46fe6803fdd163e21137ba06b81558d6ba34ad12
wpt-pr: 11426
Automatic update from web-platform-testsOffscreen canvas: make worker tests catch errors
Part of #11269.
--
wpt-commits: 8b2d92a0304de38fca9b1cee53f3769984dc0b9e
wpt-pr: 11340
Automatic update from web-platform-tests"Scroll an element into view" in HTML spec
I use assert_approx_equals here since properties of DOMRect are of type double.
For https://github.com/whatwg/html/pull/3131.
--
wpt-commits: 32f74fe70209b3df142a03957779a6d776a6f74a
wpt-pr: 10828
Automatic update from web-platform-testsHTML: Run a history navigation test in a popup to report a result (#11296)
Part of #11269.
--
wpt-commits: 2c4b6f9df0b187e0d4c1762d175e9f736492cf91
wpt-pr: 11296
Automatic update from web-platform-testsUpdate one final occurence of "w3c/web-platform-tests" (#11456)
--
wpt-commits: acba5ffb1bf7a3958bb5d70d94513912a61cbc52
wpt-pr: 11456
Automatic update from web-platform-testsAdd two screen-orientation tests and replace async by promise_test
--
wpt-commits: 8366faf9651cd188527b8b1fe6e92de3ce94650f
wpt-pr: 10701
Automatic update from web-platform-testswebrtc wpt: add cleanup to close peerconnections
adds a pc.close() to all RTCPeerConnections in promise_test
and async_test. This is codemod-powered by this:
e844b2467c/wpt-rtcpeerconnection-no-helpers
BUG=836871
Change-Id: Iee84ef938bf477a55612b6012c6de464c6aea55b
Reviewed-on: https://chromium-review.googlesource.com/1049983
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565591}
--
wpt-commits: 1622a02855f769d64d3d286eaa70a8640532310a
wpt-pr: 11455
Automatic update from web-platform-testsHTML: Use a URL that is more likely to fail to parse in img test (#11304)
Part of #1126.
--
wpt-commits: 044cb1b9a719fd2ff423e0bcd2e62dd6e547d52d
wpt-pr: 11304
Automatic update from web-platform-testswebrtc wpt: remove test_state_change_event
removes test_state_change_event which initiates a "subtest" using
a shared peerconnection resource.
BUG=836871
Change-Id: I692bb5826c83d0d36d4169858ab2872d41c03b30
Reviewed-on: https://chromium-review.googlesource.com/1074696
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562844}
--
Fire RTCPeerConnection.onsignalingstatechange in the correct order.
With this change, onsignalingstatechange always fires before the
setLocalDescription's promise resolves.
Before this change, signaling state changes were surfaced with callbacks
firing separately from the callback that setLocalDescription or
setRemoteDescription had completed. As a result, the result of a SLD/SRD
operation was surfaced in two PostTasks instead of one. This could lead
to flaky behavior where JavaScript task execeution cycles may or may not
execute between PostTasks which lead to undefined order. Also when the
signalingstatechange was surfaced to the JS thread the firing of the
event was delayed by a task execution cycle due to
ScheduleDispatchEvent.
- If both PostTasks were handled in the same cycle, the event firing
would be scheduled and the promise resolved, such that the promise's
then() is invoked just before the event fires (scheduled after
promise). This is NOT in accordance with the spec.
- If onsignalingstatechange's PostTask was handled in its own cycle,
the event would be scheduled such that by the time the
setLocalDescription's callback's PostTask occurs resolving the
promise, the event would fire before the promise's then(). This IS
in accordance with the spec.
With this change, the onsignalingstatechange event is fired without
delay, and it is processed in by the same observer that handles the
SLD/SRD callback, so the order is always guaranteed to be the same.
In addition, this CL removes the usage of
WebRTCPeerConnectionHandlerClient::SignalingState and relies on the
webrtc::PeerConnectionInterface::SignalingState enum directly. This
is part of the Onion Souping work (crbug.com/787254).
Bug: 848768, 787254
Change-Id: I7bc10439c44c6ff6beab0289975295ff2e051b9c
Reviewed-on: https://chromium-review.googlesource.com/1085302
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565291}
--
wpt-commits: eb37a99cd339ec8d0887ae82b2e66ff6b23cf7b3, 3d14e696f006162c15c1e4cdef1c7fa145af0e97
wpt-pr: 11177
Separated SimpleEdgeRange into the new UbiNodeUtils.h, updated build files, changed SimpleEdgeRange::init to SimpleEdgeRange::addTracerEdges, created bool addEdge to add new edges to the vector.
After page load the document is focused and the entire subtree is
spoken. It should only speak the name.
--HG--
extra : rebase_source : bfc5542969fa29c45b9617d873a3dba7bf1a47c2
