- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 May 2022 10:06:31 +0000
- To: public-webrtc-logs@w3.org
> The **current issue** discusses why I think minting should fail (synchronously) for `HTMLAudioElement`. OK, let's focus on this issue specifically then and if we want to discuss other issues, let's have separate issues. AIUI, you want the spec to state that creation of CropTarget for `HTMLAudioElement` should fail synchronously. This is the proposal you want to move forward here. > > Chrome team is now (maybe, I am not sure) proposing to revert these decisions and scope it down to div and iframe > > I believed you were floating the idea as a possible compromise; possibly temporary. I floated this idea to understand what was Chrome team request. > Please read [this reply](https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1139801961), which responded to the comparison with the fullscreen API. `HTMLAudioElement` means a different set of background pixels would be captured when comparing different implementations, and that's undesirable. I do not think this invalidates the point that fullscreen API is a good source of information for designing media capture region. Some APIs allow web sites to focus user attention to an HTMLAudioElement. One way is the fullscreen API. Another way might be cropping the view port on the HTMLAudioElement. As I said earlier, I could see some use of cropping to an HTMLAudioElement. This might not be the most widespread use of it but why should the spec forbid it? AIUI, your argument for forbidding it is about HTMLAudioElement opacity. I do not see how this has impact on the bounding box computation, which is what CropTarget is all about. My guess (from what you are saying) is that implementing HTMLAudioElement cropping is difficult in Chrome's implementation. Is that correct or are there other arguments? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1140961980 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 May 2022 10:06:33 UTC