Chrome 132 supports Element Capture API #25232
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
data:api
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Chrome 132 supports the Element Capture API; see https://chromestatus.com/feature/5198989277790208, and also see https://developer.chrome.com/blog/chrome-132-beta#element_capture.
Element Capture is an extension to the Screen Capture API that allows developers to restrict the captured stream to a particular DOM element.
Specifically, this PR adds:
api.BrowserCaptureMediaStreamTrack.restrictToapi.RestrictionTargetapi.RestrictionTarget.fromElement_staticI decided to add these manually because the Chrome 132 beta collector run didn't pick them up. I hope that's OK.
Test results and supporting details
Related issues
See also mdn/content#36939 for the associated content addition.