commit | 696c6dec4435324158acb58bd646e47da99d25ee | [log] [tgz] |
---|---|---|
author | Kenichi Ishibashi <bashi@chromium.org> | Tue Jan 30 00:37:39 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 30 00:37:39 2024 |
tree | 9bdf808a774f9cb31275cb2a8f7ca61abcd95950 | |
parent | c0d9f74c0973e6eff9287f1ed2229d858f550d92 [diff] |
Reland: "Allow content shell to enable the built-in DNS resolver" The original CL (https://crrev.com/c/5224044) was reverted because it made some tests flaky. The diff from the original CL is not to call NetworkService::ConfigureStubHostResolver() when running browser_tests to work around the flakiness. Not that the following original commit message is outdated because this CL isn't useful to write browser_tests any longer (but it's useful for running content_shell). [Original commit message] > Allow content shell to enable the built-in DNS resolver > > It's useful for local testing and writing browser_tests in //content. > > Move the feature flag from //chrome to //net so that > ShellContentBrowserClient can use it to determine using the built-in > DNS resolver. Bug: chromium:1521190 Change-Id: Ic02c1a69f5f302aaa346654393579946b9053de4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5232354 Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1253657}
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.