Automatic update from web-platform-tests
Address issues with parse-input-arguments-018.https.html
The test:
external/wpt/css/css-paint-api/parse-input-arguments-018.https.html
is flakily failing or crashing. This turns out to have multiple causes:
1) The generated random string that is part of inputArguments may
not be a valid identifier and thus some invocations of
registerPaint() fail before the input arguments are compared.
2) Because of the thread setup used when running the test, the
assumption about when a definition can be null does not hold.
To address (1), adjust the test to generate strings that are valid
identifiers. For (2), stay consistent with the associated
PaintWorklet's configuration by checking its `is_paint_off_thread_`
flag.
Fixed: 40786499
Change-Id: I3bd1d5eac067e7b9fbc201cb32c69c0a946baab5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5401738
Auto-Submit: Fredrik Söderquist <[email protected]>
Reviewed-by: Robert Flack <[email protected]>
Commit-Queue: Robert Flack <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1281898}
--
wpt-commits: 22e326dba564862ef9acb848682d30e5ce275d09
wpt-pr: 45402
Automatic update from web-platform-tests
[OT-PW] Make it work with OOP-R
This CL makes off-thread paint worklet work with OOP-R. OOP-R serialize
an PaintOp and stores the serialized buffer in a shared memory. GPU
then reads the memory and de-serialize it.
For off-thread paint worklet, we are producing a DrawImageRectOp. Note
that this DrawImageRectOp is different than a normal one. It is a
DrawImageRectOp that contains a DrawRecord that contains multiple
PaintOps in it. So this CL adds a special code path to serialize it,
for paint worklet DrawImageRectOp only. The way to serialize it is to
iterate over all the PaintOps inside the DrawRecord. In this way, we
do not need to change anything on the GPU de-serialize code.
We also changed the layout tests. We changed some tests, now using
fillRect instead of strokeRect.
The problem with strokeRect is that using GPU rasterization could
easily result in subpixel difference on different platforms. Using
fillRect will avoid that.
Bug: 1020238
Change-Id: Ie0aadfe217e462547cc16a273d09ec8a64f055a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1957012
Reviewed-by: Yi Gu <[email protected]>
Reviewed-by: Khushal <[email protected]>
Commit-Queue: Xida Chen <[email protected]>
Cr-Commit-Position: refs/heads/master@{#725554}
--
wpt-commits: 15e4f2b5a97b2fcd14c592f2de16cc62a82c645d
wpt-pr: 20705