Re: Collective term for Screen Capture CG APIs in MDN docs?

> On 25 Nov 2024, at 12:17, Elad Alon <eladalon@google.com> wrote:
> 
>> I think it would be a better user experience to invent a collective term for these kinds of API and have one landing page for that, which they (and future similar APIs) can live under.
> 
> This approach makes the most sense to me.
> I would expect the following API surfaces to match that category:
> The API surfaces in the canonical Screen Capture <https://www.w3.org/TR/screen-capture/> spec.
> API surfaces from specs that extend CaptureController <https://www.w3.org/TR/screen-capture/#capturecontroller> (example-1 <https://screen-share.github.io/captured-mouse-events/>, example-2 <https://w3c.github.io/mediacapture-surface-control/>).
> API surfaces that extend anything either accepted by getDisplayMedia() or returned by it. Region Capture <https://w3c.github.io/mediacapture-region/> and Element Capture <https://screen-share.github.io/element-capture/> extend the returned MediaStreamTrack, as does Capture Handle <https://w3c.github.io/mediacapture-handle/identity/index.html>.
> API surfaces that seek to provide a gentle spin on getDisplayMedia, such as getViewportMedia <https://w3c.github.io/mediacapture-viewport/>.
> IMHO, there are enough specs and API surfaces to merit this approach. Wdyt?

Great stuff, thanks for the feedback Elad. I think all of these would fit nicely under the title of “Screen Capture extensions”, so I’ll go forward and use this for the main landing page.

I can happily start to add the others in the list under this docs section as well, once I’m done with Element and Region Capture. If there are items you want to be documented as a priority, let Rachel Andrew know about them so she can add them to my official worklist.

Best,

Chris