- From: Mark Watson <watsonm@netflix.com>
- Date: Mon, 16 Sep 2019 10:13:10 +0900
- To: spec-prod@w3.org
- Cc: Greg Freedman <gregwf@netflix.com>
- Message-ID: <CAEnTvdA0CKQSHtQ5fn3zTFvtr+U9_6AKi+gseW619jAjj8789g@mail.gmail.com>
We have a (old) spec which is producing ReSpec errors of the form: 1. Couldn't match "*DOMString*" to anything in the document or in any other document cited in this specification: webidl. See how to cite to resolve the error <https://respec.org/xref/?term=DOMString&types=_CONCEPT_&cite=webidl> at: 1 <http://localhost:8080/encrypted-media-respec.html#respec-offender-error-no-matching-dfn-found-0> , 2 <http://localhost:8080/encrypted-media-respec.html#respec-offender-error-no-matching-dfn-found-1> , 3 <http://localhost:8080/encrypted-media-respec.html#respec-offender-error-no-matching-dfn-found-2> . The spec has an associated Javascript with a postprocessing script which runs through all the <a> elements looking for a handful of specific strings (including DOMString) and patching them up to have the correct href / attributes. The final HTML output is good a s result. I am wondering is Respec support for webidl references has improved and Respec is trying to manage these links itself, failing (producing the above errors) and our old postprocessor is then doing the right thing. I wonder what we need to do to have Respec's support for WebIDL references work ? Right now the source HTML just contains thinks like <a>DOMString</a>. WebIDL is getting included in our references, somehow. Perhaps because we refer to [[WEDIDL]] here and there. The spec is here: https://github.com/w3c/encrypted-media Thanks in advance, ...Mark
Received on Monday, 16 September 2019 01:13:44 UTC