Microsoft is poised to implement a groundbreaking permission policy within Chromium, designed to mitigate the issue of unexpected audio or video playback originating from hidden iframes. This update promises an enhanced browsing experience for users navigating through Chromium-based platforms like Chrome and Edge.
While contemporary browsers possess the capability to mute audio tracks, this functionality falls short in scenarios where media is already playing silently within hidden iframes. To bridge this gap, Microsoft’s innovative permission policy is set to take the reins, albeit with the expectation that developers will actively participate in its application.
According to a recent Chrome status announcement highlighted by Windows Latest, this policy, aptly named “Pause media playback on not-rendered iframes, ” has been proposed by Microsoft’s developer team. The rationale behind this initiative reflects Microsoft’s belief that continued media playback from non-rendered content can lead to negative user experiences. Existing developer workarounds have proven inadequate and can lead to noticeable performance and experience issues when rendering media content.
While specific implementation details are still forthcoming, insights gleaned from various internal documents shed light on Microsoft’s approach to regulate hidden video or audio playback through this policy.
How Microsoft’s “media-playback-while-not-visible”Policy Aims to Enhance Browsing
Currently, when developers integrate video or audio using iframes, a frequent practice involves hiding the iframe via CSS (display: none).This often stems from a desire to maintain a clean user interface, particularly on e-commerce sites where pop-up menus are common. However, this strategy can backfire; hidden media might inadvertently start playing without users’ consent.
This can result in unexpected, loud playback, causing disruption for users. Historically, developers have attempted to tackle this challenge by fully unloading and reloading the iframe, but this method can introduce serious performance drawbacks.
With the introduction of the new permission policy, web applications can instruct Chrome and Edge to automatically pause media playback whenever the iframe is not in view, resuming playback as soon as it becomes visible again. This is a significant enhancement in user experience.
The adoption of this policy is expected to significantly reduce the chances of unexpected audio or video playback while browsing in Chrome and Edge, promoting a more harmonious user experience.
As Microsoft articulately put it, the aim of this proposal is to endow web applications with the capability to exercise control over embedded media content, thereby ensuring users enjoy a seamless experience during any render state changes of the iframe. The ultimate goal is to empower developers to create more user-friendly interfaces while optimizing performance by allowing browsers to smartly manage playback for hidden content.
This new permission policy is set to be a game changer not only for Chrome but for all browsers utilizing the Chromium engine. Yet, it remains in experimental stages, and the timeline for its rollout is still under wraps.
It’s essential to point out that this is just one of several enhancements Microsoft is championing for improving browser experiences, including optimizations for HDR display color accuracy in Chrome and enhanced gameplay fluidity for controller users.
Frequently Asked Questions
1. What is the new permission policy from Microsoft regarding hidden media playback?
The new permission policy, titled “Pause media playback on not-rendered iframes, ” is aimed at preventing unexpected audio or video from playing in hidden iframes across Chromium-based browsers.
2. How will this policy impact web developers and user experience?
The policy will allow developers to pause media playback when the iframe is not visible, ensuring users do not experience unexpected sounds while browsing, thereby fostering a more pleasant and user-friendly interaction with web content.
3. When will the new permission policy be available for developers to implement?
The policy is currently in the experimental phase, and while specific rollout dates haven’t been announced, it is being actively developed for future integration into Chromium-based browsers.
Related Articles:
Ara: History Untold 1.4 Update Enhances AI, Map Generation, Combat Features, and More
19:02
Major Upgrade for Copilot in Excel
18:41
Microsoft Edge Trials AI-Enhanced MSN Feed Featuring Ads: Here’s How to Disable It
17:10
Leave a Reply ▼