commit | 6fe7ae190419d8d0359451b49bb964d0f0b273d3 | [log] [tgz] |
---|---|---|
author | L. David Baron <dbaron@chromium.org> | Thu Apr 08 14:35:03 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Apr 08 15:15:50 2021 |
tree | 07e7e71163f56afc14b2ef5b2c51872415dfe5f7 | |
parent | 05df7360eeb0d0071720fcc008e4f39275e0c413 [diff] |
Correct clipping of destination rects for filters when 3D transformed. * Make InverseMapQuadToLocalSpace flatten transform to avoid 3D clipping glitches. While cc::MathUtil::InverseMapQuadToLocalSpace was documented as requiring callers to flatten the transform, only one of the four existing callers did this. This changes it to flatten the transform internally. This fixes a bug where incorrect clipping rects were used in at least two of those three callers that were not flattening: the callers in SkiaRenderer::CalculateRPDQParams and GLRenderer::UpdateRPDQWithSkiaFilters. These callers were computing the minimal clip rect in local space (in a plane that might have a 3D transform) by transforming the clip rect (in the simple testcase, the window boundary), as a quad, into the local coordinate space, producing points that (with 3D) can have a nonzero Z components. This nonzero Z component was then dropped. However, the desired result was the point with a zero Z component in local space that would produce the correct X/Y position in device space with some arbitrary Z component in device space (that could then be dropped). This fixes the case tested in preserve3d-and-filter-no-perspective.html * Don't try clipping at all when the transform has perspective, since when there is perspective, there could be areas on the local surface that are visible even though they are outside the bounds of the quad that maps to the device's clip. This fixes the case tested in preserve3d-and-filter-with-perspective.html Bug: 923766 Change-Id: I5fbc679300ca52446552a1f5d90160309073d687 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2809095 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: David Baron <dbaron@chromium.org> Cr-Commit-Position: refs/heads/master@{#870500}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave
- For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!