Ddos 
Modern browsers now default to muting videos from less commonly visited websites. Typically, when users access ordinary webpages containing embedded videos, these videos will autoplay silently, sparing users from unexpected audio that might cause embarrassment in inappropriate settings.
However, when audio or video content is embedded via an iframe, browsers may fail to apply mute settings effectively. To address this gap, Microsoft engineers have proposed a new permission policy aimed at mitigating unintended sound playback in certain scenarios.
According to Microsoft’s engineers:
“Web applications that host embedded media content via iframes may wish to respond to application input by temporarily hiding the media content. These applications may not want to unload the entire iframe when it’s not rendered since it could generate user-perceptible performance and experience issues when showing the media content again. At the same time, the user could have a negative experience if the media continues to play and emit audio when not rendered. This proposal aims to provide web applications with the ability to control embedded media content in such a way that guarantees their users have a good experience when the iframe’s render status is changed.”
Currently, developers attempting to embed audio and video through iframes may resort to manipulating CSS display properties to conceal the embedded frames. While not all websites favor this approach, certain e-commerce platforms do adopt iframe embedding to load multimedia discreetly, allowing them to maintain a clean interface by hiding such content when pop-up menus are displayed.
The drawback of this technique is that, when using browsers like Chrome, users may still hear audio from hidden media elements—an unsettling experience for those caught unaware. Microsoft’s engineers hope to rectify this.
They have envisioned a permission policy named media-playback-while-not-visible which allows websites and developers to instruct Chromium-based browsers to pause media playback when the content is not visible, and to resume it automatically once it becomes visible again.
The caveat, however, is that this is not a universal browser feature. Instead, it requires developers to proactively adapt their codebases. Once implemented, all Chromium-based browsers—with updated engines—can adhere to this new permission policy.
Related Posts:
- Technical Details Released for XSS to RCE Vulnerability in Microsoft Office
- Google Chrome v64 ships “Mute site” feature
- ChatGPT and Sora Go Offline: OpenAI Scrambles to Restore Service Amid Global Outage
- Discover More: Google Lens Arrives on YouTube Shorts!
Donate