commit | 21e4c83ddc3b2f038f4300d0dea84906761bcc03 | [log] [tgz] |
---|---|---|
author | Vikram Pasupathy <[email protected]> | Tue Sep 27 18:37:33 2022 |
committer | Chromium LUCI CQ <[email protected]> | Tue Sep 27 18:37:33 2022 |
tree | f2f876499b9f327779540e86d56e6a9c8661302f | |
parent | 4e504eb1ab1ae54d9909f48c4c05b0ae875590d2 [diff] |
Reland "media: Update WidevineKeySystemInfo to support experiment key system" This is a reland of commit 3dcdea9f425c993742de3de0ddc3ffc7b6a5c402 We are relanding this commit as the test EncryptedMediaSupportedTypesWidevineHwSecureExperimentTest. SupportedCodecs was failing, as we failed to set the robustness separately for the normal and experimental key system. This reland now introduces logic to set the robustness separately, and now the test works as expected. Original change's description: > media: Update WidevineKeySystemInfo to support experiment key system > > This CL adds to the WidevineKeySystemInfo an experimental boolean > and the codecs that support clear lead. This is to instantiate a new > experimental key system alongside the normal key system in chrome. > Through this, we are now able to store and return different sets of > codecs when querying for hardware secure codecs, as the experimental > key system will return all hardware secure codecs and the normal key > system will return all clear lead supported hardware secure codecs. > > Bug: b/241047837 > Change-Id: I2021f2995eb3a04c6acf44b04a623f5a3f834b5c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3820526 > Commit-Queue: Vikram Pasupathy <[email protected]> > Reviewed-by: Xiaohan Wang <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1046533} Bug: b/241047837 Change-Id: I34e7fd02d85709b8b25eb1f76a341a69424fbf7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3913634 Reviewed-by: Xiaohan Wang <[email protected]> Commit-Queue: Vikram Pasupathy <[email protected]> Cr-Commit-Position: refs/heads/main@{#1051925}
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.