commit | 80c3dd7b62bb1ab52bc14ea3ca9443940f597c9d | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Tue Jun 03 09:31:36 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 03 09:31:36 2025 |
tree | 05fd80ae34c65cb346931cad2d40409a6c090c75 | |
parent | fe0e351385091ba526826bd71035a753776428a5 [diff] |
Import wpt@59d63fe03e447a73726128d9e0dcc2ca4d5c0b31 https://github.com/web-platform-tests/wpt/compare/7f97b7256...59d63fe03 Using wpt-import in Chromium 1c280426fb04bf1f8eed53772e26edc2d91b6538. With Chromium commits locally applied on WPT: 9519e61501 "QuotaExceededError: Update leftover [...] f216108c06 "Revert "Remove !important from UA select colors"" Note to gardeners: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md Directory owners for changes in this CL: dcheng@chromium.org, jarhar@chromium.org: external/wpt/domxpath NOAUTOREVERT=true R=rubber-stamper@appspot.gserviceaccount.com No-Export: true Validate-Test-Flakiness: skip Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: Iaa79d18bf394e8f06fe809fbc22404fc58beb65a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6616240 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1468603}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.