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

> [cropTo]( already returns a promise, so querying "all" documents in the single viewport captured to identify the crop target, seems reasonable to me.

I think you mean "browsing context" where you said "viewport".
Do you have a reasonable limit on how many different documents could be embedded in that browsing context?

> Cost to implementers is low on the [priority of constituencies]( when it comes to shaping APIs.

Cost to implementers is low priority, but non-zero. It's only a problem if accommodating implementers comes at a non-trivial cost to a higher-priority constituency. Does it?

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 3 February 2022 21:28:41 UTC