commit | 8a2dc60068a6c9f7c01dd88633afebba4d06ee9e | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Tue Jun 04 10:11:14 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 04 10:11:14 2024 |
tree | bb204d890f82b8320e182b1cd5dbe11dacb75ca7 | |
parent | d59e70d923e63cc8e94d13c5cdd5839aa58e73ba [diff] |
Import wpt@93263b60a46dda6382fb6f093cc529fcb4433677 https://github.com/web-platform-tests/wpt/compare/708284f76...93263b60a Using wpt-import in Chromium b617002e7d784846504c11077a63096b39919786. With Chromium commits locally applied on WPT: 4edb29252e "ruby-align: Implement the layout behavior" 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: arichiv@chromium.org, iclelland@chromium.org: external/wpt/permissions-policy mcasas@chromium.org: external/wpt/geolocation-API 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: I8730cf3024dd3968323a5ba3220b2fa853376797 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5594296 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@{#1309835}
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.