commit | 8ee3fbdbc2d83772476276ff64583fdcb2d53192 | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Tue Apr 02 12:34:58 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 02 12:34:58 2024 |
tree | 4fa3074fe3dfc368f2434f2c05c402eaabc45c21 | |
parent | 8636f002f461dd8c53e5cb4305689d6b3e5e23e2 [diff] |
Import wpt@6c6f8a91e970250b526794289906ab53e04f6f32 https://github.com/web-platform-tests/wpt/compare/cd418e26d7...6c6f8a91e9 Using wpt-import in Chromium de410d7378998500dbdf19c0ecd6027c9a8d1502. 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: japhet@chromium.org: external/wpt/fetch 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: I9b4c8f3031d7758631bedda67772531e1e57545e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5412351 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@{#1281114}
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.