Intent to Experiment: Element Capture

695 görüntüleme
İlk okunmamış mesaja atla

Elad Alon

20 Kas 2023 06:41:0020.11.2023
alıcı blink-dev

Contact emails




API for capturing a subtree of the DOM.

Given a video MediaStreamTrack obtained through pre-existing means to initiate tab-capture, Element Capture allows mutating the track to only capture a subtree of the DOM starting at a given Element.

The API bears some resemblance to the Region Capture API, but affords greater flexibility for applications, because occluding and occluded content are both excluded from the capture.

Blink component


TAG review

We are holding off on the request for a TAG review until we get some more developer feedback about the API shape.

TAG review status



Interoperability and Compatibility

Gecko: Under consideration (

WebKit: No signal (

Web developers:

Positive See upvotes and comments on the following:

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?

Goals for experimentation

* Solicit more informed Web developer feedback to validate the API shape.

* Ensure that the feature works correctly in conjunction with adjacent features.


No changes to DevTools are intended.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?


This API is supported on all desktop platforms. Mobile platforms are unsupported because screen-capture itself is unsupported on those platforms.

Is this feature fully tested by web-platform-tests?

Not yet (but we’re working on extending coverage)

Flag name on chrome://flags


Finch feature name


Tracking bug

Launch bug

Estimated milestones

Shipping on desktop


Link to entry on the Chrome Platform Status

Links to previous Intent discussions

Intent to prototype:

This intent message was generated by Chrome Platform Status.

Mike Taylor

20 Kas 2023 11:29:3120.11.2023
alıcı Elad Alon, blink-dev

Hi Elad,

Can you clarify which milestones you intend to experiment in?


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
To view this discussion on the web visit

Elad Alon

20 Kas 2023 11:35:1120.11.2023
alıcı blink-dev,, blink-dev, Elad Alon
Hi Mike. I'm asking for m121 to m126 (inclusive).

Mike Taylor

20 Kas 2023 11:39:2820.11.2023
alıcı Elad Alon, blink-dev

Thanks, LGTM to experiment from 121 to 126 inclusive.

Jan-Ivar Bruaroey

27 Kas 2023 09:53:5127.11.2023
alıcı blink-dev, Elad Alon
The Gecko position has been updated to negative. See

Elad Alon

27 Kas 2023 10:00:1127.11.2023
alıcı blink-dev,, Elad Alon
Thank you for updating, Jan-Ivar. I have now updated this information in the ChromeStatus entry. I am looking forward to carry on the discussion about your position in your standards-positions GitHub repo, in the Element Capture spec repo, in the Screen Capture CG and in the WebRTC WG.

Elad Alon

10 May 2024 06:44:5310 May
alıcı blink-dev, Elad Alon,

Hello Blink owners,

We are asking for a breaking period of 3 weeks to this API, followed by a renewed experiment for the traditional 6 milestones (2024-May-14 to 2024-Jun-04). A request that seems similar to me was granted in January 2022 for another API, and later shipped successfully with consensus with Mozilla and Apple.

At the time of writing, we have public support for this API from such companies as Zoom, Jitsi, Mux, DialPad, Whereby, Intel and Tella. Tango’s co-founder wrote “I can't emphasize enough how instrumental this specification would be for our product and user experience.” However, none of them have signed up for the OT as of yet. 

From the OT perspective:

This API allows Web developers to build novel new features; however, it requires a non-trivial investment. We are hoping that after giving more time, we will see more participation.

From the standardization perspective:

We need time to pick up discussions with Mozilla and Apple again. As Chrome’s Security and Privacy experts do not share the concerns Mozilla and Apple have previously voiced, it stands to reason that additional discussions will allow us to converge - and we will prioritize these discussions now.

Additionally, some possibilities remain for API changes that could perhaps allow for a compromise, mostly around cross-origin isolation. (Full disclosure - this is not my ideal outcome, but it’s a fallback possibility worth mentioning.)

Progress made:

  • Spec: The spec has evolved and is now more mature, dealing better with such edge cases as loss of “eligibility for restriction.”

  • TAG: Previously we held off on the request for a TAG review until we got some more developer feedback about the API shape. Having received this initial feedback, the TAG request has now been submitted.

  • Signals: Signals have been requested. Mozilla responded. We intend to prioritize this discussion with them now.

  • Feedback: Outreach for feedback from the spec community - multiple issues were filed on the spec by Web developers.

  • WPT: Coverage has recently been extended.

Reasons to run a new trial:

Gain additional feedback from new participants. Examples for remaining areas where new feedback could help include:

  • Uncover new edge cases which were not uncovered by the spec authors and reviewers, implementers and current OT participants. The current edge cases here demonstrate how non-obvious these may be.

  • Validate (or refute) the assumptions we have made about the viability of an MVP that is missing some functionality. Examples:

    • Events notifying apps when an element stops/starts being “eligible for restriction”.

    • Mechanism to force elements into an “eligible for restriction” state.

  • Encourage future OT participation by Web developers, by demonstrating that risks associated with relying on an origin trial, while real, are partially offset by a commitment to keep the OT going until discussions conclude.



Mike Taylor

10 May 2024 16:25:0310 May
alıcı Elad Alon, blink-dev,

Note: Because you're asking for a renewal of 6 milestones, this will require 3 LGTMs.

Can you clarify which milestones you're asking for? You've written "(2024-May-14 to 2024-Jun-04)" - that range maps to M125 and M126 stable releases.

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

Elad Alon

14 May 2024 12:08:1614 May
alıcı blink-dev,,, Elad Alon, Panos Astithas
I'm asking for a break-off period starting July 1 and ending July 22 (inclusive). That means that the original trial will end on June 30, and be restarted on July 23. This corresponds to breaking the original experiment early during the cycle of what would have otherwise been its final milestone (m126), the restarting the experiment over the m127-m132 range. (CC Panos for feasibility.)

Mike Taylor

14 May 2024 14:36:4314 May
alıcı Elad Alon, blink-dev,, Panos Astithas

OK - thanks for the clarification. I would ask that you get in touch with every registered origin - expiring the experiment early may be surprising.

LGTM1 to experiment from M127 to M132 inclusive.

Chris Harrelson

14 May 2024 14:40:4214 May
alıcı Mike Taylor, Elad Alon, blink-dev,, Panos Astithas

Yoav Weiss (@Shopify)

15 May 2024 10:41:3615 May
alıcı Chris Harrelson, Mike Taylor, Elad Alon, blink-dev,, Panos Astithas

Elad Alon

21 May 2024 06:05:5821 May
alıcı blink-dev, Yoav Weiss,, Elad Alon, blink-dev,, Panos Astithas, Chris Harrelson
Thank you for the LGTMs.

A quick update that we have discussed the matter with the OT Core team, and it appears to us all better to have the breaking period between June 24 (first day of break) and July 15 (first day of renewed experiment). This ensures that partners have time to mint a new token and roll it out to their production enviornment ahead of m127 shipping to Stable.
Tümünü yanıtla
Yazarı yanıtla
0 yeni ileti