commit | e06e7f146e5b2e01417406874fc34d3f873134f8 | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Wed Jan 29 09:02:39 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 29 09:02:39 2025 |
tree | a59863e44e9760420207df57db662e811e6621c1 | |
parent | c9f3d58b41c95a3e360e79915d53aaad07500a58 [diff] |
Import wpt@48b77338c179f9d42ee4a3d2ef565187f101b1e6 https://github.com/web-platform-tests/wpt/compare/1b476ffbe...48b77338c Using wpt-import in Chromium 5bcad43830ee79eacb9bbfe18dd801eb3a7fbddd. With Chromium commits locally applied on WPT: 4d43a191f5 "Clean up old popover hover utils, and de-footgun [...] 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 NOAUTOREVERT=true R=rubber-stamper@appspot.gserviceaccount.com No-Export: true Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: I542ca09f7b76344919b3704dadf6ac91b7d07ed2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6211457 Auto-Submit: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1412769}
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.