Meeting minutes
<sangwhan> can we agenda+ w3c/
Introduction
Chris: Welcome Alastor as new co-chair
Audio Session
Alastor: For Audio Session, only Safari has an implementation. Firefox is working on it, and enabling in Nightly
… Safari's behaviour when they set the session to an ambient type, which allows mixing, and you call getUserMedia() it rejects with InvalidStateError
… Discussed at TPAC, should it reject? Make a PR for getUserMedia()? Or change the audio session type
Chris: Apple folks not in the call today, it seems
Alastor: Any plans from the Chrome side?
Sangwhan: No plans, we'd want to see some large sites using it, then we'd reconsider. It's a matter of staffing
Alastor: I'm happy to share info as we progress with implementation
<sangwhan> As of today, who uses this API? Anyone know?
Chris: You have an alternative proposal?
Alastor: No, just want to confirm the TPAC 2024 decision
… I'll comment in the issue
Media Session
Chris: w3c/
Tommy: If it's an enumerated set, you could have them as inidividual action handlers. I don't see how having a separate list of actions changes much
… They seem to be looking for more control over the PiP experience, so maybe consider Document PiP instead?
Chris Looking at Media Session, more generally, we have a lot of open issues. Jan-Ivar raised #376
Tommy: On #376. we've tried not to overconstrain, so not sure what the right level to specify it would be
Chris: Let's organise doing a review of open issues
Media Playback Quality
Sangwhan: w3c/
… I want to remove corruptedFrames. I did due diligence to check for usage. One is in Brightcove, we'll do some outreach there. And Yandex
… It doesn't seem the information is used, so returning undefined should be OK
… Marcos suggested returning zero, but we've been doing that for the last 6 years
<sangwhan> https://
Sangwhan: It would be fine I think for us to remove from the spec
… Safari is returning zero
… I'll do the outreach. Yandex Advertising might be harder to contact. We can unship and see what happens
WebCodecs
<sangwhan> TL:DR we want to bring WebCodecs to CR
Eugene: I want people to look through the WebCodecs issues that are marked as CR blocking
… I intend to address those before TPAC
… If people think something is missing, apply the tag more issues
<sangwhan> CR blocking issue list: https://
Chris: Thank you for progressing that
Eugene: I hope at TPAC to talk with Mozilla and Apple folks so they're happy with how the issues are addressed
<sangwhan> availability: https://
Chris: Will schedule an earlier meeting time, during week of August 31
Sangwhan: Does Mozilla have intent to ship WebCodecs on Android?
Alastor; I can find out from the engineers working on it
TPAC 2026
Chris: TPAC is 26-30 October
… There's a planning issue in GitHub: w3c/
Sangwhan: I'll dial in. I want to discuss trimming the Charter. Many specs could be ready for CR. Now's a good time
Chris: Sounds good
[Adjourned]