-
Notifications
You must be signed in to change notification settings - Fork 38
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
Integration with HTML #156
Comments
@mounirlamouri As we're thinking about Candidate Recommendation, what shall we do with this issue? |
Not that I'm participating, but I'd highly encourage you to do this integration. You get a ton of stuff for free when you integrate with HTML, plus you get awesome feedback from the HTML editors. |
(and you potentially reduce a bunch of spec duplication) |
@marcoscaceres I'm gonna re-open this one as I think you meant closing #148 when submitting #187 |
oh, yes, sorry about that! |
Adding to the agenda to discuss whether the group thinks we should merge middle-size specifications like Picture-in-Picture to the HTML specification. The group agreed to move Media Playback Quality that's definitely short and it seems likely we wouldn't move large specification like MSE or EME. Where do we draw the line? |
Note, this isn't about merging the spec back into HTML: it's about a "fair division of labor" between the two specs. I don't think the HTML folks want to maintain that picture-in-picture specific details, but anything related to |
I understand but if we start splitting away extensions to HTMLVideoElement from this spec, we are going to have a spaghetti specification where half of it is in the HTML spec and half in the Picture-in-Picture spec. |
I seems to me that it's preferable for maintenance that the spec is kept in one place, so +1 to @mounirlamouri's comment above. |
Discussed during 11 August 2020 call. Two resolutions taken by the group: RESOLUTION: Keep the Picture-in-Picture specification as-is as it doesn't extend the HTML specification apart from partial interface |
I opened w3c/media-wg#20 for the best practices. I will close this issue. |
In #150, @domenic wrote the following. Creating an issue so it doesn't get lost.
The text was updated successfully, but these errors were encountered: