- From: Mark Watson <watsonm@netflix.com>
- Date: Mon, 16 Sep 2019 11:38:26 +0900
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: Spec Prod <spec-prod@w3.org>, Greg Freedman <gregwf@netflix.com>
- Message-ID: <CAEnTvdAYP5Mciz4pDJ1F5+oprsaeKvLrCejKHoCsiYRMn9KUjw@mail.gmail.com>
Awesome, thanks! On Mon, Sep 16, 2019 at 11:29 AM Marcos Caceres <w3c@marcosc.com> wrote: > Hi Mark, > > > On Sep 16, 2019, at 10:13 AM, Mark Watson <watsonm@netflix.com> wrote: > > > > We have a (old) spec which is producing ReSpec errors of the form: > > > > • 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 at: 1, 2, 3. > > > > 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. > > ReSpec handles this for you. > > > 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. > > Yes, we added support for linking IDL types. > > > 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>. > > Sent you a PR :) https://github.com/w3c/encrypted-media/pull/454 > > > WebIDL is getting included in our references, somehow. Perhaps because > we refer to [[WEDIDL]] here and there. > > Yes, as the spec relies on things defined in WebIDL (e.g., DOMString). > > > The spec is here: https://github.com/w3c/encrypted-media > > > > Thanks in advance, > > > > ...Mark > >
Received on Monday, 16 September 2019 02:39:00 UTC