
Mojo pipe for ApplicationMediaCapabilities was broken with the browser decoupling. This lets CastContentRendererClient receive the OnSupportedBitstreamAudioCodecsChanged events again. In upstream chromium, we will use AudioManagerAndroid to directly set support. Bug: internal 371469701 Test: Cast Dolby Digital Plus (E-AC3) content. Change-Id: I59f4c3f8df507ed69853e0e97be6722028991c69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6216724 Reviewed-by: Vigen Issahhanjan <vigeni@google.com> Reviewed-by: Simeon Anfinrud <sanfin@chromium.org> Commit-Queue: Erin Yan <yiranyan@google.com> Cr-Commit-Position: refs/heads/main@{#1416433}
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
BASE_FEATURE(kMyFeature, "my_feature", base::FEATURE_DISABLED_BY_DEFAULT);
const base::Feature* kFeatures[] = {
// ..other features
&kMyFeature
}