Re: [mediacapture-transform] Track transferability requirement adds complexity to some common use cases (#116)

> Are you insinuating this use case shouldn't be supported?

No, I'm saying it's one of several use cases, is already supported, and therefore doesn't need its own redundant API.

The argument for a dedicated API seems to rest solely on the existing API creating significant hardship. I believe I've shown with multiple working demos and shims in this issue and [#113](https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2574051986) that the difference in behavior is quite small and manageable.

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


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

Received on Tuesday, 7 January 2025 16:00:11 UTC