W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2022

Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Feb 2022 22:47:10 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1029472223-1643928429-sysbot+gh@w3.org>
> > I think you mean "browsing context" where you said "viewport".
> No, each iframe has its own [browsing context](https://html.spec.whatwg.org/multipage/browsers.html#browsing-context), which is nested (immediately or multiple levels under) the [top-level browsing context](https://html.spec.whatwg.org/multipage/browsers.html#top-level-browsing-context).
> I loosely mean all documents in this capture, which maybe translates to the top-level browsing context's document and all documents in its [nested browsing context](https://html.spec.whatwg.org/#nested-browsing-context)s of iframes that [intersect the viewport](https://html.spec.whatwg.org/#intersect-the-viewport).

I've been carrying that mistake around for a while. Thanks for enlightening me.

> > Do you have a reasonable limit on how many different documents could be embedded in that browsing context?
> Looking up the CropTarget shouldn't be the bottleneck in extreme cases, so this should scale fine.

IPC with multiple processes is neither simple, nor performant, nor robust. The cost to implementers is greatly reduced when avoiding this. What's the downside to any other constituency?

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1029472223 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 February 2022 22:47:12 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:56 UTC