commit f2de9a64bfccda835b78bfa1c0566e13c39c6721
author Christian Flach <cmfcmf@chromium.org> Thu Oct 12 09:09:34 2023
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Thu Oct 12 09:09:34 2023
tree 4779c7186f7199d87d27d1af91a168b60d55d83c
parent 04b4bf615441cefd8613f3d621ea80d337f7c234

iwa: Do not use `kIsolatedWebApps` feature flag directly

This feature flag should almost never be used directly and instead
`content::IsolatedWebAppsPolicy::AreIsolatedWebAppsEnabled` should be
used. In the renderer, the `switches::kEnableIsolatedWebAppsInRenderer`
command line flag should be used.

This CL replaces two uses:
- `apps_section.cc` used the feature flag but should use
  `AreIsolatedWebAppsEnabled`.
- `runtime_features.cc` uses both the feature flag and the command line
  switch to enable Direct Sockets. Therefore, we can remove the
  enablement based on the feature flag and instead make sure that the
  command line switch is set properly in `ShellContentBrowserClient` so
  that tests that set the feature flag continue to work.

Bug: b:289356220, 1481737
Change-Id: I61db6ae7414945d7455c43b43a1643fec45b52c8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4898690
Reviewed-by: Andrew Rayskiy <greengrape@google.com>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Christian Flach <cmfcmf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1208724}