commit | b3560c8401ca00598bf26c82ddc46f47c06213b6 | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Thu Jul 04 07:11:48 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 04 07:11:48 2024 |
tree | 938bcba9d78722edb7c132659e5f99f1602baba7 | |
parent | 55101ea043c77305a6c5e64163d0fce95212892b [diff] |
Import wpt@f0abdbbc51cab75b29c33ca1331a59dd2898adb4 https://github.com/web-platform-tests/wpt/compare/8607a1df6...f0abdbbc5 Using wpt-import in Chromium 7163501fc3aa487642d7a73f41b0dbf448065df3. With Chromium commits locally applied on WPT: d663acef31 "Use visual runs and save ShapeResults in TextMetrics" a19e45fae5 "Implement getActualBoundingBox feature for TextMetrics" 8ff864bba5 "Add failing COOP noopener-allow-popups tests and flags" 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 Validate-Test-Flakiness: skip Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: Id1ce4e37fcccf6d9c08c09ba4c690101d0ad5568 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5677193 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1323203}
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.