Contact emails
gabrielbr...@microsoft.com<mailto:gabrielbr...@microsoft.com>, 
stev...@microsoft.com
Explainer
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/IframeMediaPause/iframe_media_pausing.md
Specification
None
Summary
Adds a "media-playback-while-not-rendered" permission policy to allow embedder 
websites to pause media playback of embedded iframes which aren't rendered - 
i.e. have their "display" property set to "none". Since the only way for a 
website to halt media playback in a cross-origin iframe is to destroy the 
frame, this feature should help said websites to improve performance by 
removing the need to destroy and re-create the media-playing frame everytime 
playback needs to be paused/resumed.

Blink component
Blink>Media<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMedia>
Motivation
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.

Initial public proposal
None
TAG review
None
TAG review status
Pending
Risks

Interoperability and Compatibility
None


Gecko: No signal

WebKit: No signal
Web developers: The web community seems to be interested in this feature 
(Proposal: pause iframe media when not rendered · Issue #10208 · whatwg/html 
(github.com)<https://github.com/whatwg/html/issues/10208>). Even though we may 
need to iterate on the user-facing API, the feature is ready for 
implementation, because we anticipate that the majority of the feature 
implementation will be the same even if there are changes to be made there.
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?
None

Debuggability
None

Is this feature fully tested by 
web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
No
Flag name on chrome://flags
None
Finch feature name
None
Non-finch justification
None
Requires code in //chrome?
False
Estimated milestones
M128
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5082950457884672?gate=6024578269970432
This intent message was generated by Chrome Platform 
Status<https://chromestatus.com/>.



-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PH7PR00MB1638C5FA59458CE0BBDC1FA6D5D72%40PH7PR00MB1638.namprd00.prod.outlook.com.

Reply via email to