| commit | 6411b451cd613ed7ed96fdb635284c72ae653eca | [log] [tgz] |
|---|---|---|
| author | Alison Maher <almaher@microsoft.com> | Sat Nov 21 04:33:57 2020 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Sat Nov 21 04:52:06 2020 |
| tree | cc34ec5c0d33a014c1de7bd51ca7768359f19f1b | |
| parent | bb2b039540b0a034687938aee6d82fcfd697a693 [diff] |
Force fill/stroke color at used value time Forced colors should now happen at used value time. This change adjusts the used value of fill, stroke, -internal-visited-fill, and -internal-visited-stroke to take forced colors into account. No internal properties were needed since we only ever force fill and stroke to one value in forced colors mode. The other forced color properties will be moved in follow up changes. Note: This change will result in some functional differences with the current fill/stroke behavior in forced colors mode. SVG elements have "forced-color-adjust:none" set. Previously, SVG elements could inherit forced colors from their ancestors. Now, since we force at used value time, the used value of fill/stroke for SVG elements can no longer inherit forced colors (unless "forced-color-adjust:auto" is set by the author). The related web tests have been updated to reflect this change in behavior. Bug: 970285 Change-Id: I5bcc498a67dbd49d7b319f7f079d062d73586013 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515228 Commit-Queue: Alison Maher <almaher@microsoft.com> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#829948}
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!