-
Notifications
You must be signed in to change notification settings - Fork 4
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
Include <audio> in protocol for Remote Playback API #15
Comments
I believe this text:
... was added to clarify the scope vis-à-vis what is noted in out of scope (MSE, EME):
We can do a simple corrections to the charter to address this issue without the formal charter amendment process. Please feel free to propose text. |
Many thanks, Anssi. I propose the following:
The intent is for remote audio playback to be in scope for the CG. Note that I'm not suggesting any change with respect to MSE or EME. |
Since both @mfoltzgoogle does the proposed text sound fine? (I think you authored the original part of the text.) |
SGTM. |
Addresses Issue webscreens#15: Include <audio> in protocol for Remote Playback API Specifically mention <audio> as well as <video> as in scope for the Remote Playback API.
Fixed with a21e396. This is a simple correction, and as such no voting required for this charter change. If anyone has concerns with this correction, please reopen this issue. |
Item 4 under Scope of Work says "for the specific case of remotely playing a <video> element". Is there any reason not to include <audio>, as the receiving side of the Remote Playback API could be implemented on a headless device, for example.
The text was updated successfully, but these errors were encountered: