This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This bug is to track work necessary before proceeding to Last Call. 1. Add references (depends on ReSpec, which is bug 25506). 2. Publish a stable version of the Stream Format and Initialization Data Format Registry (see related MSE bug 25581).
For #2, we should address bug 26811 first.
3. Ensure the references are correct. For example, we are using cutting-edge Web IDL (Second Edition) features while the reference is to the CR from 2.5 years ago. Paul, do you know how we should handle this? Also, like MSE, the in-page references are to the DOM Living Standard rather than the LC WD in the references. (Speaking of MSE, it does not list DOM in the references. Should it since it references exceptions and links to the spec?)
Also, the reference for http://tools.ietf.org/html/draft-ietf-jose-json-web-key that ReSpec supports is old.
Looking at the WebIDL reference, the spec only uses the following from the second edition: Promise<?>. While this is not an issue to move the spec to LC or CR, it will be good to understand how stable the spec syntax (by asking the editor and/or looking to see if others are using it as well) and implementations are for this before moving to PR.
(In reply to Philippe Le Hegaret from comment #4) > Looking at the WebIDL reference, the spec only uses the following from the > second edition: Promise<?>. The spec also uses: * maplike (once bug 26372 is implemented) * DOMException in its new location (it is to be removed from the DOM spec: http://www.w3.org/TR/dom/#errors). This could be reverted if necessary.
plh, you should know by know that bz and others have explained several times that there are fundamental problems with v1 that are not getting fixed (no resources). Please stop encouraging WGs to waste time on it.
(IDL v1 that is.)
At this point, it's not clear to me what needs to be done to be honest. I asked to see a plan and I'm still waiting for one.
I was talking about WebIDL re plan, not about EME itself btw.
https://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0521.html and around is plenty clear.
yes, it proposes some options, but I don't know which one got chosen.
Looking at an early upcoming draft of WebIDL v1, I see the following: - https://ylafon.github.io/webidl/l1-respec.html#idl-exceptions - https://ylafon.github.io/webidl/l1-respec.html#idl-promise However, maplike is not part of it http://heycam.github.io/webidl/#idl-maplike
regarding maplike: [[ OK. So I'm fine with maplike/setlike being considered unstable at the moment, because they are. ]] https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0097.html
* #1 is resolved. * #2 is now tracked by https://github.com/w3c/encrypted-media/issues/104. * #3 is now tracked by https://github.com/w3c/encrypted-media/issues/107. (https://github.com/w3c/encrypted-media/issues/74 was also related.) * Comment #3 regarding JWK is now tracked by https://github.com/w3c/encrypted-media/issues/108.