commit | 1ebd9648f556cf120a941d0b2d44b6bfb23f67ae | [log] [tgz] |
---|---|---|
author | Anders Hartvoll Ruud <andruud@chromium.org> | Thu Jan 04 11:35:22 2024 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Jan 04 11:52:06 2024 |
tree | 4a5a6e2aa1f0fcd5a2c31baee1e03ee4355049ab | |
parent | f61ca76190eff03c2660a7525d04572f93191b18 [diff] |
[@scope] Produce kScopeActivation relations for scoped nesting When parsing style rules that are immediate children of an @scope rule, any compound selector which contains either :scope or '&' is prepended with RelationType::kScopeActivation. This relation is what triggers the "figure out if we're indeed in scope, and what the scoping root is"- behavior during SelectorChecker, and without the kScopeActivation, we'll just fall back to the regular behavior for :scope (i.e. it matches :root in the normal cases). This CL fixes a bug which caused missing kScopeActivations for nested style rules within @scope, e.g.: @scope (a) { b { /* :scope needs to refer to 'a' here */ :scope:not(&) { ... } } } This doesn't work, because we're basing the kScopeActivation emit/no-emit decision on the nesting type of the *immediate* parent rule, which in this case is CSSNestingType::kNesting. We need to know whether any ancestor rule is an @scope rule, and so we propagate a flag for this, and base the emit/no-emit decision on this instead. Fixed: 1512217 Change-Id: I35d28489dd8255badd2e9a9c911fda3e2541bb52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5164291 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Auto-Submit: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1242853}
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:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If 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 wpt.live and w3c-test.org.
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!