commit | ffafa390f6714838504d38724d2b8dbf90971ae1 | [log] [tgz] |
---|---|---|
author | Hung-Hsien Chen <hunghsienchen@chromium.org> | Tue Feb 18 02:56:10 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 18 02:56:10 2025 |
tree | a38b2092cda3c7210fee91cdb701ecff326c3380 | |
parent | 81ebe83e0a74076cd98c182114e39e24513c7bc6 [diff] |
Audio QS: Listen to Voice Isolation UI changes Before this CL, the audio quick setting view is updated when the active input device is changed, and it gets the UI appearance (which toggle to show in audio QS) from the CrasAudioHandler. When the active input device is changed to one that would change the UI appearance, the audio QS would get the old (wrong) UI appearance from the CrasAudioHandler, which is updated later on. This is fixed by listening to OnVoiceIsolationUIAppearanceChanged of CrasAudioHandler::AudioObserver and updating the view. testing/xvfb.py out/Default/ash_pixeltests \ --gtest_filter='*AudioDetailedViewPixelTest*' testing/xvfb.py out/Default/ash_unittests \ --gtest_filter='*AudioDetailedViewTest*' Fixed: b:397157568 Fixed: b:397156973 Test: autoninja -C out/Default ash_pixeltests && \ Test: autoninja -C out/Default ash_unittests && \ Change-Id: I92f89c0abfb5fffcc2ae325d81c5c2f949d1ea8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6275470 Reviewed-by: Li-Yu Yu <aaronyu@google.com> Commit-Queue: Hung-Hsien Chen <hunghsienchen@chromium.org> Reviewed-by: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1421198}
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.