commit | ca8e78f6365796458e3b2162d9cffbd6fd38315f | [log] [tgz] |
---|---|---|
author | Yoshisato Yanagisawa <yyanagisawa@chromium.org> | Wed Jul 20 01:33:39 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 20 01:33:39 2022 |
tree | 6d28d17476b185096a244200ceb25741b05ca5f6 | |
parent | e8f604f4f8a85debf8359e0f02efa90fdbb2ac1d [diff] |
Revert "Send error to console when the fetch failed for dedicated workers." This reverts commit dced83f79f1a28df56330e1c6a7783ec00abb915. Reason for revert: This CL brought flakiness of the WPT. That might be because the CL did not take care of how the script load failed and it might show message for flaky network. Let me revert the CL and think the better way. Original change's description: > Send error to console when the fetch failed for dedicated workers. > > For ease of understanding the failure of fetching scripts in > dedicated workers, the failure will be shown in the console log. > > Developers will see the error log if the load was prohibited due to > COEP for example. > > Change-Id: I6fce6f2b0f49e96f5e9ff41f06f2d8ad8383d701 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3721722 > Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org> > Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1019973} Change-Id: Ia08d0d7457511440c585978c1e9b42b8faa93129 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3769676 Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026051}
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.