Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)

> OK, let's focus on this issue specifically then and if we want to discuss other issues, let's have separate issues.

I have focused on this topic **exclusively** in this issue here. I would appreciate it if you could point out where this was ambiguous in my comments. (Note: My responses to others' off-topic messages do not count as me being off-topic myself.)

> 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.

You understand correctly.

> I do not think this invalidates the point that fullscreen API is a good source of information for designing media capture region.

I too think that the fullscreen API is a good source of information. As soon as Jan-Ivar brought it up, I went out and examined its specification as well as implementation - as covered in my previous comments. What I found was that:
1. Most important - there are substantive differences between the two APIs which mean we cannot apply them identically. This has been explained in previous comments.
2. Less important - the fullscreen API is inconsistently implemented. I argue that this is NOT just a bug. It's indicative of how HTMLAudioElement is an uninteresting target for the fullscreen API and is rightfully prioritized too low to fix. It's similarly uninteresting as a crop-target.
3. Interestingly, **HTMLScriptElement** is a valid target for the fullscreen API! So I think a few design decisions were made there that I would not want to replicate.

> 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?

As stated in my previous messages, the main reason is that it makes for a poor crop-target. It's a footgun. (Because of the inherent, non-cross-compat shape differences.)

> 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.

That the definition of a bounding box yields is **meaningful** does not mean it's **useful**.

> My guess (from what you are saying) is that implementing HTMLAudioElement cropping is difficult in Chrome's implementation.

I have no reason to suspect that it's difficult in Chrome's implementation.

> Is that correct or are there other arguments?

What about `HTMLScriptElement`? Is this a clearer example of why some subtypes don't make sense?

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/51#issuecomment-1142015965 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 31 May 2022 11:34:35 UTC