commit | c06c66aad52c5d4d64e43a5b9fb9657eb224e43d | [log] [tgz] |
---|---|---|
author | Vikram Pasupathy <vpasupathy@chromium.org> | Wed May 14 14:32:29 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 14 14:32:29 2025 |
tree | 4bf9fcc9fbc4144c9935f62d2ecddf66ae7e9246 | |
parent | e829e2e6ef2cfd5c47eeeaa0632cc0c30b9d6652 [diff] |
media: Fix MediaCapabilities reporting for audio only configs In a previous CL http://crrev.com/c/6364074, we moved the KeySystem check below audio and video support. However, this introduced a bug because in audio-only configs, the code previously had an optimization to return DecodeSupport early, without checking KeySystemConfigs. With this code change, we now bring back checking the key system support in the audio-only optimized path, and introduce a browser test of audio only config with a key system specified. This now also introduces a KeySystemAccess check to verify that KeySystemAccess object is not null when a valid KeySystemAccess is provided. Bug: 417251427 Change-Id: I0c29cc8e3597789b9ae85d936710f8e6c01af76c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6538246 Commit-Queue: Vikram Pasupathy <vpasupathy@chromium.org> Reviewed-by: Sangbaek Park <sangbaekpark@chromium.org> Reviewed-by: Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/main@{#1460070}
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.