commit | 4231644367ce411104f5852d4e449c02d3d36609 | [log] [tgz] |
---|---|---|
author | Baitinq <manuelpalenzuelamerino@gmail.com> | Thu Jul 27 20:08:51 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 27 20:08:51 2023 |
tree | 98a82628b78c8c939a7cb78eee622b4619af937d | |
parent | 13c5f5e31f35fce40f89460bc531be65d670cb7a [diff] |
Hide media metadata from media controllers if required This CL implements the ability for embedders to obscure the media metadata from the OS's media controllers. This media metadata will simply be replaced by some placeholder metadata. This is done by making use of the embedder-specific MediaSessionClient API to both check if we need to obscure the media metadata and also get the placeholders we should replace the media metadata by. As in Chromium's case the implementation of the MediaSessionClient API (ChromeMediaSessionClient) specifies that the media metadata should be hidden if its playing in an Incognito session, that will be the new behavior introduced by this CL. The actual obscuring of the metadata is just implemented by intercepting calls to the SystemMediaControls API and replacing the metadata with placeholder metadata when needed. Bug: 1447545 Change-Id: If8fdf1703cb4eda4652f17d1fdd515567a5dcfde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4651207 Reviewed-by: Chris Bookholt <bookholt@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Filipa Senra <fsenra@google.com> Commit-Queue: Manuel Palenzuela Merino <manuelpalenzuelamerino@gmail.com> Reviewed-by: Zaina Al-Mashni <zalmashni@google.com> Cr-Commit-Position: refs/heads/main@{#1176245}
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.