Skip to content

Conversation

@youennf
Copy link
Collaborator

@youennf youennf commented Nov 14, 2025

@alvestrand
Copy link
Collaborator

This change removes the "empty" value. Are we clear that we don't need this one?

@youennf
Copy link
Collaborator Author

youennf commented Nov 17, 2025

Fixes #278.

@youennf
Copy link
Collaborator Author

youennf commented Nov 17, 2025

Are we clear that we don't need this one?

The only case where empty may be used in Chromium is after the video frame is written/transferred.
But this is not specced anywhere and it does not seem that useful.

@guidou, thoughts? Would you like any clarification work as discussed in #278?

@guidou
Copy link
Collaborator

guidou commented Nov 18, 2025

Chromium uses "empty" only with the old API. With the standard version the frame keeps old metadata values after writing (at least the tests test that and implementations do that), so "empty" is never used in the spec and can be removed.

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.

3 participants