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

playoutDelay should use milliseconds. #155

Closed
jan-ivar opened this issue Apr 5, 2023 · 2 comments · Fixed by #160
Closed

playoutDelay should use milliseconds. #155

jan-ivar opened this issue Apr 5, 2023 · 2 comments · Fixed by #160

Comments

@jan-ivar
Copy link
Member

jan-ivar commented Apr 5, 2023

W3C design principle § 8.3. Use milliseconds for time measurement says... well, exactly that.

Let's not spread the mistake from stats of using seconds (which I feel personally responsible for) to more specs!

Since no browser implements this feature correctly yet — fortunately, Chrome only implements a cousin named playoutDelayHint that fails to throw on input validation — I still see an opportunity to correct this.

@jan-ivar
Copy link
Member Author

jan-ivar commented Apr 6, 2023

A reason to contain this to stats would be fixing it someday with something like getStats({timeunit: "milliseconds"})

@dontcallmedom-bot
Copy link

This issue was mentioned in WEBRTCWG-2023-04-18 (Page 81)

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 a pull request may close this issue.

2 participants