- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Apr 2022 16:10:09 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-region: == Spec erroneously limits self-capture to same-document/iframe == There's some [evidence](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1029472223) this spec is confusing browsing context with top-level browsing context throughout. As a result, the spec's limiting of cropping to elements in the same document that is calling cropTo, appears erroneous: * In [ยง 4. Scope](https://w3c.github.io/mediacapture-region/#scope): _"As presently defined, [cropTo](https://w3c.github.io/mediacapture-region/#dom-browsercapturemediastreamtrack-cropto)(ID) returns a [rejected](https://webidl.spec.whatwg.org/#reject) [Promise](https://webidl.spec.whatwg.org/#idl-promise) if the ID is not associated with an [Element](https://dom.spec.whatwg.org/#element) within the current [browsing context](https://html.spec.whatwg.org/multipage/browsers.html#browsing-context)."_ The "current browsing context" of a cropTo() call from an iframe is the browsing context local to that iframe only. In contrast, most of the hard discussions I've taken part in in this repo have been around cross-origin serialization of cropTarget, which implies this is not the case. I therefore think fixing this is mostly editorial. Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/40 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 April 2022 16:10:10 UTC