- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Mar 2022 15:01:47 +0000
- To: public-webrtc-logs@w3.org
Agree the current definition is flawed. Editorially, I also don't think we should outsource "validity" to any sub-algorithm like this, because what's valid when something is called has a lot to do with when and where that call is made. So I prefer `cropTo` spell out its input validation steps explicitly and synchronously. The cropTo validation steps seem to me to be (unrelated to produceCropTarget): 1. If the target's element is no longer around, bail 2. If that element is no longer in a document, bail 3. If that document is not this (track)'s captured [top-level browsing context](https://html.spec.whatwg.org/multipage/browsers.html#top-level-browsing-context)'s [active document](https://html.spec.whatwg.org/multipage/browsers.html#active-document), or not an [active document](https://html.spec.whatwg.org/multipage/browsers.html#active-document) in one of this (track)'s captured [top-level browsing context](https://html.spec.whatwg.org/multipage/browsers.html#top-level-browsing-context)'s [nested browsing context](https://html.spec.whatwg.org/multipage/browsers.html#nested-browsing-context)s, bail. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/29#issuecomment-1074008247 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 March 2022 15:01:48 UTC