Add browser test for restrictOwnAudio, and switches for autosharing screen with audio. Add browser tests for restrictOwnAudio that checks if the correct audio deviceId is created with the possible values for restrictOwnAudio and suppressLocalAudioPlayback. This test needs a screen to be auto picked. A new chrome switch (kAutoSelectScreenCaptureSource) is added to accomplish that. There is and old kAutoSelectDesktopCaptureSource that can autoselect screens based on name. But the screens have different names on different platforms, and can be different on the same platform if you have one or several screens. So the old switch is hard to use. This new kAutoSelectScreenCaptureSource autoselects any screen, so you loose control, but you don't need to know the name of the screen. The test also need that system audio is shared. So a kSystemAudioCaptureDefaultChecked is added to change so system audio is shared by default when sharing a screen or window. The kScreenCaptureAudioDefaultUnchecked is renamed to kTabCaptureAudioDefaultUnchecked). From the ScreenCapture prefix it was hard to understand it only effected the share audio toggle on the share tab selection, so it is renamed to have a TabCapture prefix. Bug: 415952276 Change-Id: I8caf07ebf483f96a881694358b38cf33947f04b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6611139 Reviewed-by: Tove Petersson <tovep@chromium.org> Reviewed-by: Tomas Gunnarsson <tommi@chromium.org> Commit-Queue: Olov Brändström <brandstrom@chromium.org> Cr-Commit-Position: refs/heads/main@{#1478558}
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.