Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial state of cloned tracks #65

Open
eladalon1983 opened this issue Jun 9, 2022 · 1 comment
Open

Initial state of cloned tracks #65

eladalon1983 opened this issue Jun 9, 2022 · 1 comment

Comments

@eladalon1983
Copy link
Member

eladalon1983 commented Jun 9, 2022

The spec currently reads:

clone()
When a BrowserCaptureMediaStreamTrack is cloned, the user agent MUST produce a track which is initially uncropped, regardless of the crop-state of the original track.

Rethinking this, I don't see how that serve Web developers. The most natural thing to do when cloning is to clone as much of the state as possible - that's what a developer would expect.

If a developer wishes to hand off an uncropped version of the track, they can do the following:

const clonedTrack = track.clone();
await track.cropTo();
// Hand it off.
eladalon1983 added a commit that referenced this issue Jun 9, 2022
@youennf
Copy link
Contributor

youennf commented Jun 14, 2022

That seems reasonable. This would need a change in the way we do cloning, which will be made easier once we merge w3c/mediacapture-main#873.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants