
Cast needs both render process ID and render frame ID for resolving URL requests to owning render frame / web contents. Bug: internal b/116784351 Test: Build cast_shell and run unittests Change-Id: Ib1913e41f33410241fe4d63fffa6c1ee68e18be3 Reviewed-on: https://chromium-review.googlesource.com/c/1280930 Reviewed-by: Luke Halliwell <halliwell@chromium.org> Commit-Queue: Tavis Maclellan <maclellant@chromium.org> Cr-Commit-Position: refs/heads/master@{#600766}
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.cc
so it lives alongside existing features - Add your new feature to the list of
kFeatures
incast_features.cc
const base::Feature kMyFeature{"my_feature", base::FEATURE_DISABLED_BY_DEFAULT};
const base::Feature* kFeatures[] = {
// ..other features
&kMyFeature
}