html
html copied to clipboard
Editorial: Export concepts used by Encrypted Media Extensions
The list includes:
- media resource
- media data
- blocked media element
- potentially playing
- direction of playback
- [x] At least two implementers are interested (and none opposed): N/A
- [x] Tests are written and can be reviewed and commented upon at: N/A
- [x] Implementation bugs are filed: N/A
(See WHATWG Working Mode: Changes for more details.)
:boom: Error: Wattsi server error :boom:
PR Preview failed to build. (Last tried on Jan 15, 2021, 8:00 AM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
:rotating_light: Wattsi Server - Wattsi Server is the web service used to build the WHATWG HTML spec.
:link: Related URL
Parsing MDN data...
Parsing...
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.
How does the layering work with EME? I'm not sure a clean integration was ever attempted here.
We're currently updating the EME spec in the Media WG, so would like to reference these definitions. Is there anything we need to do to for this PR to be ready to merge?
Having some kind of answer to my question would be good. As well as if the layering is still lacking some idea of how we might address that going forward.
Someone will also have to rebase this it seems (or create a new PR).
Having some kind of answer to my question would be good. As well as if the layering is still lacking some idea of how we might address that going forward.
Anne, can you help educate us on layering or help us with links to educate ourselves? My experience in spec-world is limited.
The naive answer would seem to be that EME layers on top of HTML video, and to that end, we need these definitions exported so we can refer to them properly from the EME spec.
I'm only looking at this from the point of view of EME & HTML video. Are you asking us to consider layering anything else in specific in relation to these?
Thanks!
@joeyparrish there's a whole section that monkey patches HTML. That's the kind of thing I would expect to be integrated better.
HTML does sometimes call out to other specifications at well-defined times in its processing models (e.g., in update the rendering), but when other specifications start monkey patching HTML it's hard to maintain a robust setup.
Hope that helps!