commit | 714272d72474a209387880626d7ae36aacee8b5e | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Wed Oct 19 22:48:38 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 19 22:48:38 2022 |
tree | 8061a8231a32007f08caa41f16c205a3c1a74d5e | |
parent | d359dfe42bc0d2187f060b722068f24a63b502dd [diff] |
Import wpt@d1e78524fc8991f8ec84aa99d25ec75055dfac92 Using wpt-import in Chromium 4fe5c9a6c5803f5f07ad79743acc2e6c2a2478c0. With Chromium commits locally applied on WPT: 4c9aa435ea "[Mixed Content] WPT tests for sandboxed documents." c386df4690 "[Private Network Access] Test targetAddressSpace more thoroughly." Note to sheriffs: 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-wpt-identity-fyi-rel,linux-wpt-input-fyi-rel,linux-blink-rel Change-Id: I5761d6730a373023d9898c1695799c69eac66b3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3965174 Auto-Submit: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1061291}
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.