-
Notifications
You must be signed in to change notification settings - Fork 15
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
Different behavior when onaddtrack is fired for element.captureStream #100
Comments
I think you should probably look at the event.
|
I would agree the spec can be clearer on this. I think the question boils down to whether the events fire sync or async in the text:
I'll also note that the |
Consider the following code:
The test video file test-av-384k-44100Hz-1ch-320x240-30fps-10kfr.webm has both audio and video tracks. This code is almost identical to the one in the web platform test.
Below are the logs from the code above:
Chrome 125.0.6422.141:
Firefox 126.0:
In Chrome, the
onaddtrack
is fired twice, however even with the first event, both audio and video tracks are present in the stream. In Firefox, theonaddtrack
is fired twice, but the first event only has the audio track, and the second event has both audio and video tracks.I wonder which behavior is correct. The current web platform test assumes that the behavior in Chrome is correct (it checks only the first event), but it may be an implementation detail of Chrome.
The text was updated successfully, but these errors were encountered: