Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Chromium changes: https://chromium.googlesource.com/chromium/src/+/54c6ac50650c82426bcb363a57b18dc47a1dedc4 commit 54c6ac50650c82426bcb363a57b18dc47a1dedc4 Author: John Rummell <jrummell@chromium.org> Date: Tue Sep 24 23:52:06 2019 +0000 Use manifest.json to determine features supported by Widevine CDM on Linux Use the manifest.json file bundled with Widevine CDM (on Linux) to determine the features supported by Widevine rather than have them explicitly specified in code. This is handled by the component updater for Windows and Mac, so extending it to Linux now that the Widevine CDM for Linux is in a separate directory. Bug: 971433 https://chromium.googlesource.com/chromium/src/+/a539416c1f041af93e054d1cd397f895762022bc commit a539416c1f041af93e054d1cd397f895762022bc Author: John Rummell <jrummell@chromium.org> Date: Thu Oct 3 21:39:30 2019 +0000 Enable component updated Widevine CDM on desktop Linux On Linux the Widevine CDM is loaded into the zygote at startup. When the component updater runs sometime later and finds a newer version of the Widevine CDM, don't register it as the newer version can't be used. Instead, similar to Flash, save the path to the new Widevine CDM in the file latest-component-updated-widevine-cdm. Next time at startup this file will be checked, and if it references a usable Widevine CDM, use this version instead of the bundled CDM. Tested this by running Chrome built with an older version of the Widevine CDM, and then checking chrome://components for a newer (QA) version. As there is one, it gets updated. When restarting Chrome, the newer version is loaded. In both cases Widevine content was played using Shaka. Bug: 971433
- Loading branch information