| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Is it correct that we do the same today for Windows as is stated in the title?
On Windows, this function checks if the OS is Windows 11 or newer,
aligning the logic with `IsRestrictOwnAudioSupported()`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Is it correct that we do the same today for Windows as is stated in the title?
On Windows, this function checks if the OS is Windows 11 or newer,
aligning the logic with `IsRestrictOwnAudioSupported()`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
bool IsApplicationAudioCaptureSupported() {Can we move everything to media_switches? It does not seem there are any benefits in splitting logic between two places
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Can we move everything to media_switches? It does not seem there are any benefits in splitting logic between two places
I've moved the feature flags to media_switches, to be able to move all logic there.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hi @to...@chromium.org. I added you as a reviewer since I need an owner of desktop_media_picker_views.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
base::win::GetVersion() >= base::win::Version::WIN11;Should this really be checked as part of the feature test.
When cleaning up these feature flags, I assume that this test will be done in the implementation files. Can it be done there already? Or is it part of the rollout to start on Win11 and later expand to other Windows versions?
base::win::GetVersion() >= base::win::Version::WIN11;Can you add a comment about why it is disabled on Windows 10? From what I gather, application audio is supported on at least some versions of Windows 10?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
base::win::GetVersion() >= base::win::Version::WIN11;Should this really be checked as part of the feature test.
When cleaning up these feature flags, I assume that this test will be done in the implementation files. Can it be done there already? Or is it part of the rollout to start on Win11 and later expand to other Windows versions?
I followed the style of the existing functions, e.g. `IsMacCatapSystemLoopbackCaptureSupported()` and`IsWindowsProcessLoopbackCaptureSupported()`.
base::win::GetVersion() >= base::win::Version::WIN11;Can you add a comment about why it is disabled on Windows 10? From what I gather, application audio is supported on at least some versions of Windows 10?
This uses the same API as RestrictOwnAudio. `IsRestrictOwnAudioSupported()` checks for windows 11, so it should be the same for application audio capture. I'm not the expert, so if you want a better answer I could dig for it, but the reason we just enable for win11 is that we can't see if the user uses a win10 that support this API or not.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (WindowAudioPreference() ==Why there is no update of this logic in the follow-up CL?
base::win::GetVersion() >= base::win::Version::WIN11;Olov BrändströmCan you add a comment about why it is disabled on Windows 10? From what I gather, application audio is supported on at least some versions of Windows 10?
This uses the same API as RestrictOwnAudio. `IsRestrictOwnAudioSupported()` checks for windows 11, so it should be the same for application audio capture. I'm not the expert, so if you want a better answer I could dig for it, but the reason we just enable for win11 is that we can't see if the user uses a win10 that support this API or not.
IsWindowsProcessLoopbackCaptureSupported() should be used instead.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Why there is no update of this logic in the follow-up CL?
The code reads: If audio should be offered in the window tab, the info box should say "application audio" if {windowAudio: window} and application audio loopback is supported, and "system audio" otherwise. That is true before and after any change.
The difference in the follow-up CL logic is just how often audio should be offered in the window tab, i.e. what `ShouldOfferWindowAudio()` returns.
base::win::GetVersion() >= base::win::Version::WIN11;Olov BrändströmCan you add a comment about why it is disabled on Windows 10? From what I gather, application audio is supported on at least some versions of Windows 10?
Olga SharonovaThis uses the same API as RestrictOwnAudio. `IsRestrictOwnAudioSupported()` checks for windows 11, so it should be the same for application audio capture. I'm not the expert, so if you want a better answer I could dig for it, but the reason we just enable for win11 is that we can't see if the user uses a win10 that support this API or not.
IsWindowsProcessLoopbackCaptureSupported() should be used instead.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |