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

I don't see a problem with HTMLAudioElement:
<img height=100 src="https://user-images.githubusercontent.com/3136226/170575753-98d4e99c-47a3-4b99-9220-38fc01ffd117.png">

> It looks like some Elements are not sensible crop-targets.

I think focusing on what can and cannot be a "target" at the time of minting is the wrong place to triage what can and cannot be cropped to.

Lots of elements won't make sense to cropTo (but you can't know that at the point of minting):
1. Elements properties that control their visibility (e.g. `controls`) may change at any time 
1. Elements may become attached or become detatched to a captured document at any time
2. A `div` may become 0x0 pixels or huge depending on CSS changes at any time
3. An element may become obscured or invisible at any time, rendering its appearance irrelevant to what's captured

In short, the live cropping algorithm is going to need to handle situations occurring that produce no output. Trying to use input validation to ween what goes into this basket seems of low value.

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


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

Received on Thursday, 26 May 2022 20:51:14 UTC