commit | 9d9ac4bd6a1880869b59c96a5408d36ba445a012 | [log] [tgz] |
---|---|---|
author | Gabriel Brito <gabrielbrito@microsoft.com> | Thu Oct 31 03:15:40 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 31 03:15:40 2024 |
tree | 9d2677a8478ce4162ddb1fdfc0f3a166161dbcd5 | |
parent | 171434b9c2aea10c136a0b12315f387d179af7ee [diff] |
[WebAudio] Implement the AudioContext interrupted state This CL implements the AudioContext "interrupted" state and the interruption methods behind a feature flag. This feature's explainer can be found at: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/AudioContextInterruptedState/explainer.md Even though this feature is not fully testable by using WPTs (it needs an external agent/feature to cause the interruption), unit tests have been added to make sure that the feature behaves in accordance to the explainer. This feature can be controlling by enabling the AudioContextInterruptedState flag. The following cmd line can be used: chrome.exe --enable-features=AudioContextInterruptedState Chrome Status: https://chromestatus.com/feature/5172068166139904 I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/GgSvU1BZZRU Bug: 374805121 Change-Id: Ib86b903ac623c3e18deaf7a3caa39a8c91b1808f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5943336 Reviewed-by: Michael Wilson <mjwilson@chromium.org> Auto-Submit: Gabriel Brito <gabrielbrito@microsoft.com> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Commit-Queue: Gabriel Brito <gabrielbrito@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1376076}
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.