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

> 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).

> 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.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1029463302 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:32:23 UTC