Automatic update from web-platform-testsFixed config.json not being used in TestEnvironment (#10494)
Added a check in the TestEnvironment load_config so it overrides the
default config when present.
Closes https://github.com/w3c/web-platform-tests/issues/8181
--
wpt-commits: 8824132b3278f9ad126764689464e515d9a62473
wpt-pr: 10494
Automatic update from web-platform-testsPaymentHandler: Not allow to call operation if event is not trusted
Related spec change:
https://github.com/w3c/payment-handler/pull/294
Bug: 833530
Change-Id: I65d0e01bb5b6bfdd44925b90ba98837161cc136b
Reviewed-on: https://chromium-review.googlesource.com/1013664
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#551238}
--
wpt-commits: e08f2142aa8e98034966994966e02fff3747bdf8
wpt-pr: 10483
Automatic update from web-platform-testsApply automatic pull for AudioWorkletNode with zero output
Spec: https://webaudio.github.io/web-audio-api/#rendering-loop (Step 9.5)
The AudioWorkletNode with zero output must be pulled by the renderer.
The actual output will be ignored just like AnalyserNode.
Bug: 831245
Test: LayoutTests/external/wpt/webaudio/the-audio-api/the-audioworklet-interface/audioworkletnode-automatic-pull.https.html
Change-Id: If9bd27d6c4bfeecdcd2dd4c8445459afd8593e85
Reviewed-on: https://chromium-review.googlesource.com/1014388
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551210}
--
wpt-commits: 7eed33a59decf3541af0b014968008e2c55a9f92
wpt-pr: 10496
Automatic update from web-platform-testsUpdate mozprofile from 0.29 to 1.0.0 (#10453)
--
wpt-commits: 25b6727b41d8ad70dcf8da8d8057e2b85f7cc2ce
wpt-pr: 10453
These issues were previously ignored due to the nature of our global import
rules. They need to be fixed before that rule can be updated.
MozReview-Commit-ID: DCChktTc5TW
--HG--
extra : rebase_source : cffb1c9762191c579d1397c8169e6e7635d229da
extra : histedit_source : dea59ddd2daaae52069c5faceae9149a4f08dd73
The PNG data generated in this test creates a 100x100 image with opaque green
pixels in the left 50px and fully transparent pixels in the right 49px. The 1px
vertical strip of pixels at pixel column 50 are green pixels with .66 alpha.
The test was failing because it supplied a shape-image-threshold of .25, and
thus was floating by 51px instead of the intended 50px. This change modifies
the test to use a shape-image-threshold of .7, generating the intended 50px
float area.
MozReview-Commit-ID: GJtym0p95yk
--HG--
extra : rebase_source : f6388475db46a5ced29cf401ce12ae9c28cb81f3
The test shape-outside-circle-027.html has two issues that prevent it from
matching the reference image. For that test to pass, the text must be floated
right by 75 pixels. The two issues are:
1) The circle is defined as 35% of 170 pixels, which calculates to 59.5px.
Since the shape-margin is 15px, this makes the total offset less than the
target of 75px.
2) The circle is offset upwards by 10 pixels, which introduces a slight angle
between the block start of the text and the center of the circle. The
cosine of this small angle is slightly less than 1, which reduces the
offset by some amount.
The changes made here specify the circle radius in whole pixels, and move the
center of the circle such that it is between the block start and block end of
the floated text, ensuring that the full width of the circle + shape-margin
will be used for calculating the float area.
MozReview-Commit-ID: JQ9Mc3GU4tW
--HG--
extra : rebase_source : 18af61015feb06f7fa0b1884dbfd97f927238f8d
https://www.w3.org/TR/css-shapes-1/#funcdef-ellipse states that the
grammar for ellipse is:
ellipse() = ellipse( [<shape-radius>{2}]? [at <position>]? )
This permits either 0 or 2 shape-radius tokens, but not 1. These two tests
use 1 shape-radius token and do not parse correctly.
https://www.w3.org/TR/css-shapes-1/#typedef-shape-radius states that omitted
shape-radius values default to closest-side. This change updates these two
tests to add the closest-side value for the missing shape-radius tokens.
MozReview-Commit-ID: 9UKxJel1b50
--HG--
extra : rebase_source : 2688982811417fe91fea2ba9c202de7a822c290c
https://www.w3.org/TR/CSS2/visudet.html#propdef-line-height specifies that
line-height is given an initial value of normal, which is defined:
Tells user agents to set the used value to a "reasonable" value based on the
font of the element. The value has the same meaning as <number>. We recommend
a used value for 'normal' between 1.0 to 1.2. The computed value is 'normal'.
These tests are designed to work correctly if and only if the line-height
is 1. This change specifies line-height: 1 explicitly.
MozReview-Commit-ID: 3Ueassok0f
--HG--
extra : rebase_source : a6036fa620a67e6e48c795da963f9dd2835beebc
The test added in this patch fails without the corresponding code changes
(specifically the second gGetComputedTimingTests test fails the comparison of
the 'easing' member).
MozReview-Commit-ID: 9eyXruVrPuN
--HG--
extra : rebase_source : 927f55c0670bf770e03d38eb876202efbb700c1e
Normally this sort of change could be filed under "needless churn",
but by appending new files to this list we end up with constant
merge conflicts.
MozReview-Commit-ID: HnaIN2d5fOa
--HG--
extra : rebase_source : b6661417d4e7afeb8e73abe5c2ea15714b4f7dbd
Running wpt occasionally failed due to an issue starting the ws[s]
servers. This turns out to be a deadlock caused by a logging lock
being inherited into the child process, sometimes in a locked
state. As a workaround, after spawning the subprocess, we reload the
logging module in order to clear any existing lock. This is pretty
much a hack, but it's the fastest path to a solution to a critical issue.
