d8e77216ad
The idea is to separate the existing dependencies into the multiple targets, so that we ultimately drop the dependency on //content from "user_agent" in the future. The "browser_util" target has been split into: - content_settings - permissions - user_agent Most users will need only the "embedder_support" target (which has some command-line switches) or the "user_agent" target, which should also bring in much fewer dependencies than before. Bug: 389970327, 391914246 Change-Id: I027084756ba955a3f511e1324ad986753c525743 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6246155 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: David Bertoni <dbertoni@chromium.org> Reviewed-by: Mike Taylor <miketaylr@chromium.org> Reviewed-by: Sean Topping <seantopping@chromium.org> Reviewed-by: Colin Blundell <blundell@chromium.org> Reviewed-by: David Dorwin <ddorwin@chromium.org> Reviewed-by: Eric Seckler <eseckler@chromium.org> Commit-Queue: Raphael Kubo da Costa <kubo@igalia.com> Reviewed-by: Bo Liu <boliu@chromium.org> Cr-Commit-Position: refs/heads/main@{#1423063}
Cast base
cast_features
This file contains tools for checking the feature state of all of the features which affect Cast products. Cast features build upon the Chrome feature system. Some aspects of Cast require the feature system to work differently, however, so some additional logic has been layered on top. Details are available in comments of the header file. The basics are:
- If you are adding a new feature, add it to
cast_features.ccso it lives alongside existing features - Add your new feature to the list of
kFeaturesincast_features.cc
BASE_FEATURE(kMyFeature, "my_feature", base::FEATURE_DISABLED_BY_DEFAULT);
const base::Feature* kFeatures[] = {
// ..other features
&kMyFeature
}