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

> 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
> 2. Elements may become attached or become detatched to a captured document at any time
> 3. A div may become 0x0 pixels or huge depending on CSS changes at any time
> 4. An element may become obscured or invisible at any time, rendering its appearance irrelevant to what's captured


These events belong to the category of things that could happen even after cropping. They are covered in the spec, and is in fact the basis for many of the design decisions behind the spec. But we're not discussing these.

Rather, we are discussing something that is known before minting and cannot change - the type of Element. If it is extremely unlikely that Web-developers would use a target of a certain type, then time spent expanding the definition to include it, and time to implement it, is time wasted, that could otherwise by used productively (to the benefit of all constituencies). We should seriously consider allowing user agents to reject some types.

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Friday, 27 May 2022 08:28:48 UTC