- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 May 2020 15:34:58 +0000
- To: public-secondscreen@w3.org
I believe that the problem is not with the spec itself: all IDL terms are now exported by default by ReSpec (the [`RemotePlayback` definition](https://w3c.github.io/remote-playback/#dom-remoteplayback) in the Editor's Draft does have a `data-export` attribute in particular), but the TR version was published too long ago to have the appropriate attributes. Bikeshed does not have definitions from the RemotePlayback API in its database because that spec is not in Shepherd yet, which Bikeshed uses to build its database of terms. The current solution is to "[contact the project maintainer](https://github.com/tabatkins/bikeshed/issues/) and ask them to register your spec in Shepherd, so its definitions will be available to everyone else" (extract from [Bikeshed's documentation](https://tabatkins.github.io/bikeshed/#dfn-contract)). I'll raise that there. I'm not entirely sure that Shepherd can extract terms from an ED that uses Respec though (because it parses the source, not the processed document). -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/137#issuecomment-624722073 using your GitHub account
Received on Wednesday, 6 May 2020 15:35:00 UTC