Skip to content

Introduce MediaStreamTrackHandle#121

Merged
guidou merged 6 commits intow3c:mainfrom
youennf:introduce-mediastreamtrackhandle
Jan 15, 2026
Merged

Introduce MediaStreamTrackHandle#121
guidou merged 6 commits intow3c:mainfrom
youennf:introduce-mediastreamtrackhandle

Conversation

@youennf
Copy link
Copy Markdown
Contributor

@youennf youennf commented Dec 17, 2025

Fixes #116


Preview | Diff

@youennf youennf force-pushed the introduce-mediastreamtrackhandle branch from 4de6e61 to 67b8e42 Compare December 17, 2025 17:11
@youennf youennf force-pushed the introduce-mediastreamtrackhandle branch from 67b8e42 to 2d5d00d Compare December 17, 2025 17:13
Copy link
Copy Markdown
Member

@jan-ivar jan-ivar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if we start with a strong reference to simplify.

@alvestrand
Copy link
Copy Markdown
Contributor

Without having thought about it too much, it seems simpler to assume that a MediaStreamTrackHandle has a strong reference to its MediaStreamTrack; weak references are a bit harder to reason about. We should identify an use case where this is an issue before making things more complex.

@youennf youennf requested review from guidou and jan-ivar January 8, 2026 15:18
@guidou guidou merged commit dfaaaaa into w3c:main Jan 15, 2026
2 checks passed
github-actions bot added a commit that referenced this pull request Jan 15, 2026
SHA: dfaaaaa
Reason: push, by guidou

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

Track transferability requirement adds complexity to some common use cases

4 participants