- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 May 2022 21:39:26 +0000
- To: public-webrtc-logs@w3.org
> Here's a possible compromise. ... redefine CropTarget.fromElement() as accepting (HTMLDivElement or HTMLIFrameElement) @eladalon1983 between what positions would that be a compromise? > I can't begin to imagine how my intent is not clear from the original issue. What elements do you mean when you say _"[elements like HTMLAudioElement?](https://github.com/w3c/mediacapture-region/issues/51#)"_ Do you include HTMLVideoElement? I so I would not have guessed that from the OP. @youennf also [said](https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1139465705): _"I have difficulties following what we are trying to discuss here"_, which is why I suggested opening a fresh issue describing the problem anew. He proceeded to say/ask you: > It seems what we are after here is something different, maybe scoping the spec down to only supporting div/iframe (?). This is a different discussion that we can certainly have. Is having that discussion here your intent? I see no direct response from you to that statement/question. > What I asked was - is it ["sensible"](https://github.com/w3c/mediacapture-region/issues/51#issue-1247028422) to support HTMLAudioElement? Yes it's sensible and has [consensus](https://www.w3.org/TR/mediacapture-region/#producecroptarget-method), which means I don't have to defend it (even though [I did](https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1139889375)), rather you have to explain why it's _not_ sensible. To help clarify, do you think it is sensible to support HTMLVideoElement? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1140058668 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 May 2022 21:39:28 UTC